Borrowing it
Nothing to install: this file belongs to AgiFlow/claude-code-prompt-analysis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AgiFlow/claude-code-prompt-analysis/main/.claude/commands/review.mdgit clone --depth 1 https://github.com/AgiFlow/claude-code-prompt-analysisWrote 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/agiflow/claude-code-prompt-analysis/review)<a href="https://agentmods.dev/commands/agiflow/claude-code-prompt-analysis/review"><img src="https://agentmods.dev/badge/commands/agiflow/claude-code-prompt-analysis/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/agiflow/claude-code-prompt-analysis/review"><img src="https://agentmods.dev/badge/commands/agiflow/claude-code-prompt-analysis/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.00164 |
| Opus 5.5 | $0.00000 | $0.00066 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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
Review File
Review the specified file for code quality, best practices, potential issues, and improvements.
Usage
/review <file_path>
Instructions
Please review the file at: {{arg1}}
Analyze the code for:
-
Code Quality
- Readability and maintainability
- Naming conventions
- Code organization and structure
-
Best Practices
- Language-specific conventions
- Design patterns usage
- Error handling
-
Potential Issues
- Bugs or logic errors
- Performance concerns
- Security vulnerabilities
- Edge cases not handled
-
Improvements
- Refactoring opportunities
- Optimization suggestions
- Documentation needs
Provide specific, actionable feedback with code examples where applicable.
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 · 39 lines · 0 tokens per session scan A 68741dad623b
review is a command published in the GitHub repository AgiFlow/claude-code-prompt-analysis (20 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 164 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
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).