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.
npx agentmods add commands/penwyp/claudepreference/m-review-codegit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWhat 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 | $0.00000 | $0.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
m-review-code 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Workflow: Comprehensive Analysis & Report Generation
Target: $ARGUMENTS (Default: latest commits of current branch)
Scope: Analyze code changes, architecture patterns, and implementation quality
Execution Steps
-
Architecture & Pattern Analysis
- Review repository patterns, service layers, and migration strategies
- Assess system design decisions and structural changes
-
Security & Multi-tenant Validation
- Check authentication, authorization, and tenant isolation
- Identify potential security vulnerabilities and access control issues
-
Functional Completeness Verification
- Ensure all requirements are implemented with proper edge case handling
- Validate input validation, error handling, and boundary conditions
-
Code Quality Assessment
- Identify code smells, anti-patterns, and duplicated logic
- Detect potential runtime issues: race conditions, memory leaks, null pointer exceptions
-
Test Coverage Evaluation
- Assess unit and integration test coverage gaps
- Review test quality and edge case coverage
-
Third-party Library Opportunities
- Suggest robust external libraries for current implementations
- Identify opportunities to reduce custom code complexity
-
Generate Bilingual Report
- Compile findings into structured markdown format
- Save to
docs/workspaces/review-MM-dd-HH-mm-ss.md
Output Format
English Report
Present findings in the following sections:
functionalCompleteness
- Requirements implementation status
- Edge case handling assessment
- Missing functionality identification
criticalBugs
- Potential crashes, panics, or system failures
- Security vulnerabilities and data exposure risks
- Performance bottlenecks and resource leaks
badSmells
- Code anti-patterns and design issues
- Duplicated or overly complex logic
- Maintainability concerns
thirdPartyOpportunities
- External library suggestions for current implementations
- Benefits and integration considerations
- Risk assessment for library adoption
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.
- 2d ago First seen · 112 lines · 0 tokens per session scan A 7685d825ad14
m-review-code is a command published in the GitHub repository penwyp/ClaudePreference (137 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 760 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.