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/KhaiTrang1995/claude-code-structureWrote 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/khaitrang1995/claude-code-structure/review)<a href="https://agentmods.dev/commands/khaitrang1995/claude-code-structure/review"><img src="https://agentmods.dev/badge/commands/khaitrang1995/claude-code-structure/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/khaitrang1995/claude-code-structure/review"><img src="https://agentmods.dev/badge/commands/khaitrang1995/claude-code-structure/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.00000 | $0.00192 |
| Opus 5.5 | $0.00000 | $0.00077 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
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 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.
What it actually says
/project:review – Code Review Command
Usage
/project:review [file or diff]
Description
Performs a structured code review covering:
- Correctness – Logic errors, edge cases, off-by-one errors
- Security – OWASP Top 10 issues, injection risks, exposed secrets
- Performance – N+1 queries, unnecessary re-renders, large payloads
- Style – Adherence to
.claude/rules/code-style.md - Tests – Adequate coverage per
.claude/rules/testing.md
Output Format
Provide feedback grouped by severity:
- 🔴 Critical – Must fix before merge
- 🟡 Warning – Should fix
- 🟢 Suggestion – Nice to have
Shell Step
git diff HEAD~1 HEAD
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 · 26 lines · 0 tokens per session scan A 04b06e34c7af
review is a command published in the GitHub repository KhaiTrang1995/claude-code-structure (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 192 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-31.
Other commands, from other repositories
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.
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.
post
Post the current OCR review to a GitHub PR.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.