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/widnyana/eyay-toolkitsWrote 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/widnyana/eyay-toolkits/cg-review)<a href="https://agentmods.dev/commands/widnyana/eyay-toolkits/cg-review"><img src="https://agentmods.dev/badge/commands/widnyana/eyay-toolkits/cg-review/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/widnyana/eyay-toolkits/cg-review"><img src="https://agentmods.dev/badge/commands/widnyana/eyay-toolkits/cg-review.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.00015 | $0.00822 |
| Opus 5 | $0.00008 | $0.00411 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
cg-review 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review target: $ARGUMENTS
If no target was given above, review the current uncommitted diff instead:
!git diff
Reconstruct the Design Graph the code ACTUALLY implements — not the one the author intended. Then diff it against the method's completeness checklist. Every mismatch is a finding.
Graph Protocol — quick reference
Emit ALL sections below, in this order, with these markers:
PROBLEM: <one line — what this code does, as implemented>
X → DesignGraph<A, E, R>
│ │ │ │ │
│ │ │ │ └─ R: what each node needs (§5)
│ │ │ └──── E: where the graph breaks (§4)
│ │ └─────── A: what flows through nodes (§2)
│ │
│ └─ nodes = functions, edges = data flow
│
└─ the problem
SHAPES: records · IDs · state variants · named errors (as actually present)
GRAPH: ascii call graph of the implemented code, annotated inline:
R: deps · E: err ⟳retry[×n] → ↯escape(alt) | ☠die · 🔒 unknown→trusted
CARDINALITY: node (1) one-shot · (N) many over time · (T) time-bounded
BOUNDARIES: every untrusted→trusted crossing (parse, don't validate)
BEHAVIOR: orthogonal layers that wrap without changing the graph
SCOPE: resources: acquire@x → release@x (structural, not convention)
TEST LAYERS: can this graph run with substituted R? if not — hidden deps
VERDICT: <matches | mismatches listed by § number>
Findings checklist (group findings by § number)
- §1 Shapes — unnamed errors (stringly-typed failures), bare-string IDs, missing state variants.
- §2 A — happy path unreadable; error handling woven through it (A/E tangled).
- §3 Cardinality —
(N)implemented as(1), unbounded collection treated as one-shot, missing cache/dedupe for(T). - §4 E — unmarked breaks, silent swallowing,
☠dieused for domain errors, retry on non-transient failures. - §5 R — hidden dependencies, node constructs its own infrastructure, world-mocking required to test one node.
- §6 Boundary — validation scattered inside the graph instead of parsing at edges, trusted shapes built from untrusted data without conversion.
- §7 Behavior — retry/timeout/logging hard-coded into business logic instead of wrapping orthogonally.
- §8 Scope — resources released by convention or not at all; cleanup as TODO.
- §9 Test — graph can't run with substituted R.
- §10 Structure — per-layer E scoping violated (inner errors leak through); divergent strategies not marked.
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.
- 10d ago First seen · 73 lines · 15 tokens per session scan A 53fc6c1e443b
cg-review is a command published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 822 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.
review-pack
Inspect Soliton's risk-adaptive context pack for a PR or local diff (Step 1 + Step 2 + Step 2.5 + Step 2.75; no agent dispatch).
review
Command "review" from KhaiTrang1995/claude-code-structure, covering /project:review – code review command, usage, description, output format and shell step.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.