Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/druide67/asiai/bench.degit clone --depth 1 https://github.com/druide67/asiaiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/druide67/asiai/bench.de)<a href="https://agentmods.dev/commands/druide67/asiai/bench.de"><img src="https://agentmods.dev/badge/commands/druide67/asiai/bench.de.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00038 | $0.01820 |
| Opus 5 | $0.00019 | $0.00910 |
| Sonnet 5 | $0.00008 | $0.00364 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade B, and why
bench.de scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `--power` | Kreuzvalidierung der Leistung mit sudo powermetrics (IOReport immer aktiv) | How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
asiai bench
Engine-übergreifender Benchmark mit standardisierten Prompts.
Verwendung
asiai bench [options]
Optionen
| Option | Beschreibung |
|---|---|
-m, --model MODEL |
Zu benchmarkendes Modell (Standard: Auto-Erkennung) |
-e, --engines LIST |
Engines filtern (z.B. ollama,lmstudio,mlxlm) |
-p, --prompts LIST |
Prompt-Typen: code, tool_call, reasoning, long_gen |
-r, --runs N |
Durchläufe pro Prompt (Standard: 3, für Median + Stddev) |
--power |
Kreuzvalidierung der Leistung mit sudo powermetrics (IOReport immer aktiv) |
--context-size SIZE |
Kontext-Füll-Prompt: 4k, 16k, 32k, 64k |
--export FILE |
Ergebnisse als JSON-Datei exportieren |
-H, --history PERIOD |
Vergangene Benchmarks anzeigen (z.B. 7d, 24h) |
-Q, --quick |
Schnellbenchmark: 1 Prompt (code), 1 Durchlauf (~15 Sekunden) |
--compare MODEL [MODEL...] |
Modellübergreifender Vergleich (2-8 Modelle, gegenseitig exklusiv mit -m) |
--card |
Teilbare Benchmark-Karte generieren (SVG lokal, PNG mit --share) |
--share |
Ergebnisse in die Community-Benchmark-Datenbank übermitteln |
Beispiel
asiai bench -m qwen3.5 --runs 3 --power
Mac Mini M4 Pro — Apple M4 Pro RAM: 64.0 GB (42% used) Pressure: normal
Benchmark: qwen3.5
Engine tok/s (±stddev) Tokens Duration TTFT VRAM Thermal
────────── ───────────────── ───────── ────────── ──────── ────────── ──────────
lmstudio 72.6 ± 0.0 (stable) 435 6.20s 0.28s — nominal
ollama 30.4 ± 0.1 (stable) 448 15.28s 0.25s 26.0 GB nominal
Winner: lmstudio (2.4x faster)
Power: lmstudio 13.2W (5.52 tok/s/W) — ollama 16.0W (1.89 tok/s/W)
Prompts
Vier standardisierte Prompts testen verschiedene Generierungsmuster:
| Name | Tokens | Testet |
|---|---|---|
code |
512 | Strukturierte Code-Generierung (BST in Python) |
tool_call |
256 | JSON-Funktionsaufrufe / Instruktionsbefolgung |
reasoning |
384 | Mehrstufiges Mathematikproblem |
long_gen |
1024 | Dauerhafter Durchsatz (Bash-Skript) |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 170 lines · 38 tokens per session scan B e0ce7b40af22
bench.de is a command published in the GitHub repository druide67/asiai (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,820 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
integrate-pipeline
Integrate a new document parsing pipeline into ParseBench: $ARGUMENTS.
create-task
Automatically scan a dbt project and generate ADE-Bench benchmark tasks via pattern matching.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.