Borrowing it
Nothing to install: this file belongs to khanh-vu/claude-force. 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/khanh-vu/claude-force/main/.claude/commands/review.mdgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/review)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/review"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/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.00008 | $0.02003 |
| Opus 5 | $0.00004 | $0.01001 |
| Sonnet 5 | $0.00002 | $0.00401 |
| Haiku 4.5 | $0.00001 | $0.00200 |
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 6d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Command
Analyze an existing project's .claude setup and provide recommendations for claude-force integration.
Purpose
The /review command helps you:
- Assess existing .claude folder structure
- Detect technology stack (languages, frameworks, databases)
- Recommend appropriate agents for your project
- Identify potential issues or improvements
- Get project statistics and insights
Usage
Basic Review (Current Directory)
/review
Review Specific Directory
/review /path/to/project
With Output Format Options
/review --format markdown
/review --format json
/review --output report.md
What Gets Analyzed
Project Statistics
- Total files and lines of code
- File distribution by extension
- Project size (bytes)
- Test file detection
- Git repository status
Technology Stack Detection
Languages (12+):
- Python, JavaScript, TypeScript, Java, Go, Rust
- C++, C, Ruby, PHP, Swift, Kotlin
Frameworks (9+):
- React, Vue.js, Angular, Next.js
- FastAPI, Django, Flask, Express.js, Spring Boot
Databases (5+):
- PostgreSQL, MySQL, MongoDB, Redis, SQLite
Infrastructure & Tools:
- Docker, Kubernetes, CI/CD pipelines
- Cloud providers (AWS, GCP, Azure)
Agent Recommendations
Based on detected technologies, recommends:
- Relevant agents with confidence scores
- Agent priorities (primary, secondary, optional)
- Skill matches and capabilities
Security Analysis
- Skips sensitive files (credentials, keys, .env)
- Validates project paths (prevents path traversal)
- Respects system boundaries
Implementation
You should execute this command by:
- Import the ReviewCommand class:
from claude_force.commands.review import ReviewCommand
from pathlib import Path
-
Determine the project path:
- If user provides a path argument, use that
- Otherwise, use current working directory
- Validate the path exists and is a directory
-
Execute the review:
# Create command instance
command = ReviewCommand(Path(project_path))
# Run analysis
result = command.execute()
# Format output based on user preference
if format_preference == "markdown":
output = command.format_markdown(result)
elif format_preference == "json":
output = command.format_json(result)
else:
output = command.format_markdown(result) # default
# Display to user
print(output)
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.
- 6d ago First seen · 339 lines · 8 tokens per session scan A 4bf78bcdf712
review is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 2,003 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.