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/matt-dionis/claude-code-configs/reviewgit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/matt-dionis/claude-code-configs/review)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/review"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/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.01032 |
| Opus 5 | $0.00004 | $0.00516 |
| Sonnet 5 | $0.00002 | $0.00206 |
| Haiku 4.5 | $0.00001 | $0.00103 |
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory MCP Server Code Review
Perform a comprehensive review of $ARGUMENTS with focus on MCP protocol compliance and memory system integrity:
Critical Security & Safety
- Data Isolation: Verify companion/user boundary enforcement
- SQL Injection: Check all database queries for parameterization
- Embedding Leakage: Ensure vector data doesn't cross tenant boundaries
- Auth Tokens: Validate secure storage and transmission
- API Keys: Check for hardcoded credentials (OpenAI, Neon)
- Session Hijacking: Review session management implementation
MCP Protocol Compliance
- JSON-RPC 2.0: Validate message format compliance
- Error Codes: Use standard MCP error codes (-32700 to -32603)
- Tool Registration: Verify proper tool manifest structure
- Parameter Validation: Check Zod schemas match MCP expectations
- Response Format: Ensure consistent response structure
- Streaming Support: Validate partial result handling
Memory System Integrity
- Vector Dimensions: Ensure consistent embedding dimensions (1536 for OpenAI)
- Index Configuration: Review IVFFlat/HNSW parameters
- Memory Lifecycle: Check expiration and archival logic
- Consolidation Rules: Validate memory merging algorithms
- Importance Scoring: Review decay and update mechanisms
- Deduplication: Check for duplicate memory prevention
Performance Optimization
- N+1 Queries: Identify and fix database query patterns
- Vector Search: Optimize similarity thresholds and limits
- Index Usage: Verify proper index hints and scans
- Connection Pooling: Check pool size and timeout settings
- Batch Operations: Look for opportunities to batch DB operations
- Caching Strategy: Review memory and query result caching
Database & Schema
- Migration Safety: Check for backward compatibility
- Transaction Boundaries: Verify ACID compliance
- Deadlock Prevention: Review lock ordering
- Foreign Keys: Ensure referential integrity
- Soft Deletes: Validate is_archived handling
- Timestamps: Check timezone handling
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 · 148 lines · 8 tokens per session scan A bfa1f865f2a5
review is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 1,032 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-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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.