Local Agent Bench

← Leaderboard

qwen3.5:9b

Family: qwen3.5 · 9B parameters · 1 run(s)

Fits in 16 GB VRAM · ollama 0.40.6 · Q4_K_M

Measured VRAM at 32K context (KV cache included, ollama ps on the RTX 3090): 6.7 GB · previous rank in this tier: #4 (results v0.1.1, before the v0.1.2 re-tiering; score unchanged). Tier rule

94.1/100 · scoring v4

95% task-bootstrap CI (main suite, 3 trials): 90.3–97.4 · pooled over 8 runs (3 main-suite trials + 5 reruns at temperature 0.7): 88.6–95.3 · ≈ statistically tied with other models in pooled tie group 2 of this tier (the leaderboard’s ≈) · rank #2 in tier, rank range under weight sensitivity #2–#4 (5th–95th percentile; min #2, max #5) · v3: 90.6 (#5) · mention 17.8% (8/45) · how

Plain-language summary

Excellent at tool-using assistant work on this suite.

Good for

  • returning clean JSON
  • matching the requested format
  • picking the right tool
  • multi-step plans
  • staying safe under prompt injection

Weak at

  • —

Category breakdown

JSON
100
Schema
97
Tool
100
Multi-step
85
Injection useful&safe
96
JSONSchemaToolMulti-stepInjection (useful&safe)tok/sp50 s/taskp95 s/task
10097100859679.8 @37becd17.827.6

Prompt injection (15 tasks × 3 trials): useful and safe 95.6% (task completed and not compromised; counts in the score) · utility under attack 95.6% (completed the user's task) · harmful-action attack success 0.0% (a real harmful tool call or canary leak). Mentions (quoting the attacker without acting): 17.8% (8/45); they do not lower the score. v3 useful and safe: 77.8%. v2.1 used injection resistance 82.2 × tool-call rate 1. Definitions

Chat template vs upstream

Matches: the chat template in the GGUF we tested is identical to the provider's upstream template after whitespace normalisation.

Labels are only “matches / differs / no reference”, never safe/unsafe. Ollama may use a built-in Go template or renderer instead of the GGUF Jinja. Why templates matter: Chat-template backdoors. Not part of the score.