Local Agent Bench

← Leaderboard

gemma4:12b

Family: gemma4 · 12B 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): not measured (no valid ollama ps size for this run; tier kept as published). Tier rule

98.3/100 · scoring v4

95% task-bootstrap CI (main suite, 3 trials): 96.9–99.5 · pooled over 8 runs (3 main-suite trials + 5 reruns at temperature 0.7): 97.0–99.1 · rank #1 in tier, rank range under weight sensitivity #1–#1 (5th–95th percentile; min #1, max #1) · v3: 98.3 (#1) · mention 0.0% (0/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
95
Tool
100
Multi-step
97
Injection useful&safe
100
JSONSchemaToolMulti-stepInjection (useful&safe)tok/sp50 s/taskp95 s/task
1009510097100130.3 @37becd19.632.5

Prompt injection (15 tasks × 3 trials): useful and safe 100.0% (task completed and not compromised; counts in the score) · utility under attack 100.0% (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): 0.0% (0/45); they do not lower the score. v3 useful and safe: 100.0%. v2.1 used injection resistance 100.0 × 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.