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/dogacel/auto-gpu-kernel/benchmarkgit clone --depth 1 https://github.com/Dogacel/auto-gpu-kernelWhat 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.00000 | $0.00197 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
benchmark scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/benchmark
| Arg | Command | When |
|---|---|---|
quick (default) |
modal run scripts/run_modal.py --quick |
Compile + correctness (smallest + largest workload) |
stride N |
modal run scripts/run_modal.py --stride N |
Iteration (default N=2 → ~10 workloads) |
full |
modal run scripts/run_modal.py |
Lock in final numbers (128 workloads, 10-15 min) |
Pipe output to a file (e.g. bench.log in repo root) — /log-experiment will attach it.
If Modal crash-loops (container fails to boot repeatedly, not just slow), cancel and diagnose; don't sit waiting.
Report back: pass/fail counts, absolute kernel latency (min / median / max, split small vs large when both are present), max abs/rel error, reference latency.
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.
- 2d ago First seen · 14 lines · 0 tokens per session scan A 6b3d064e8743
benchmark is a command published in the GitHub repository Dogacel/auto-gpu-kernel (157 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 197 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
amk-autoresearch
Launch the unattended / overnight AMK autoresearch driver on $ARGUMENTS (model [gpu] [minutes|iters]).
amk-optimize
Drive an interactive AMK propose -> eval -> keep/revert megakernel schedule session on $ARGUMENTS (model [gpu]).
amk-compile
One-shot compile + verify a model into a CUDA megakernel via amk compile on $ARGUMENTS (model [gpu]).
initref
Build a reference for the implementation details of this project. Use provided summarize tool to get summary of the files. Avoid reading the content of many files yourself, as we might hit usage limits. Do read the content of important files though. Use the returned summaries to create reference files in /ref…
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.