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.
git clone --depth 1 https://github.com/justrach/codegraff2Wrote 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/justrach/codegraff2/check)<a href="https://agentmods.dev/commands/justrach/codegraff2/check"><img src="https://agentmods.dev/badge/commands/justrach/codegraff2/check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/justrach/codegraff2/check"><img src="https://agentmods.dev/badge/commands/justrach/codegraff2/check.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00096 |
| Opus 5.5 | $0.00004 | $0.00038 |
| Sonnet 5.5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
check 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 1mo 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.
This is a copy
100% identical to check — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Run the
lintandtestcommands and verify if everything is fine. cargo +nightly fmt --all; cargo +nightly clippy --fix --allow-staged --allow-dirty --workspace cargo insta test --accept --unreferenced=delete - Fix every issue found in the process
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.
- 1mo ago First seen · 10 lines · 11 tokens per session scan A 27689fa5bb2e
check is a command published in the GitHub repository justrach/codegraff2 (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 96 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to check, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
compliance-check
Ejecuta todas las verificaciones de compliance de reglas.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
build
Invoke the agent-skills:incremental-implementation skill alongside agent-skills:test-driven-development.