Borrowing it
Nothing to install: this file belongs to sijeeshmiziha/visionagent. 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/sijeeshmiziha/visionagent/main/.claude/commands/review.mdgit clone --depth 1 https://github.com/sijeeshmiziha/visionagentWrote 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/sijeeshmiziha/visionagent/review)<a href="https://agentmods.dev/commands/sijeeshmiziha/visionagent/review"><img src="https://agentmods.dev/badge/commands/sijeeshmiziha/visionagent/review.svg" alt="Measured on agentmods" 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.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Perform a thorough code review of changes in this branch.
Arguments
$ARGUMENTS (Optional: a specific file path, PR number, or "staged" for staged changes only)
Review Process
1. Identify Changes
git diff main...HEAD --name-only
Or if reviewing staged:
git diff --staged --name-only
2. Read Every Changed File
Read each changed file completely. Don't skim — understand the full context.
3. Review Checklist
Type Safety:
- No
anytypes insrc/(tests/examples may use them) - All public functions have explicit return types
- Zod schemas match the actual data being validated
-
import typeused for type-only imports
Correctness:
- Error cases are handled (not silently swallowed)
- Async/await used correctly (no floating promises)
- No race conditions in agent execution loops
- Edge cases covered (empty inputs, null/undefined, API errors)
Architecture:
- New tools follow the ToolConfig pattern
- New modules are exported through proper index.ts chain
- No circular imports
- New features are exported from src/index.ts if public API
Testing:
- New functionality has corresponding tests in
tests/ - Tests use MSW mocks (not real API calls)
- Tests cover happy path AND error cases
- Coverage doesn't regress
Code Quality:
- No dead code or unused imports
- Consistent naming with existing codebase
- No console.log left in production code (use logger)
- Comments explain WHY, not WHAT
Documentation:
- New public API documented in README.md
- CHANGELOG.md updated
- JSDoc on exported functions/interfaces
4. Security Check
- No API keys or secrets hardcoded
- No user input passed directly to shell commands
- No path traversal vulnerabilities in file operations
5. Run Validation
npm run ci
6. Report
Provide:
- Summary of what the change does
- Issues found (if any) with file:line references
- Suggested improvements
- Overall verdict: APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION
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.
- 8d ago First seen · 91 lines · 0 tokens per session scan A d88114379842
review is a command published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 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
audit-freshness
Audit de fraîcheur multi-stack (versions + best practices) via équipe d'agents parallèles Context7 + Web.
pre-merge-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
review-code
Trigger a comprehensive code review on recent changes or specified files.
code-review
A review of uncommitted code changes for security problems, quality issues, and common maintenance concerns. A commit is a saved change in a version-control system such as Git.
check-architecture
Angular Architecture Review.