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/klapaudius/symfony-mcp-server/pre-commit-reviewgit clone --depth 1 https://github.com/klapaudius/symfony-mcp-serverWrote 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/klapaudius/symfony-mcp-server/pre-commit-review)<a href="https://agentmods.dev/commands/klapaudius/symfony-mcp-server/pre-commit-review"><img src="https://agentmods.dev/badge/commands/klapaudius/symfony-mcp-server/pre-commit-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 | $0.00000 | $0.00394 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
pre-commit-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 4d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions: pre-commit-review
Please perform a comprehensive code review for the uncommited changes. Follow these steps:
1. Code Quality Review
Analyze all changes and evaluate:
Architecture & Design:
- Does the code follow Symfony >6.4 best practices and conventions?
- Does the code follow single responsibility principle with clear separation of concerns?
- Are new dependencies justified and properly integrated?
Security & Performance:
- Are there any security vulnerabilities or exposed sensitive data?
- Is caching implemented where beneficial?
- Does memory usage is optimal?
Code Standards:
- Does the code follow PSR standards and project conventions?
- Are variable names and methods descriptive and consistent?
- Is error handling comprehensive and appropriate?
- Are comments and documentation adequate?
- Does all methods have a PHPDocs block?
- Does test method's names are snake_case_named?
Testing & Reliability:
- Are unit tests present for the new functionality?
- Do integration tests cover the main workflows?
- Are edge cases and error scenarios tested?
- Is the test coverage adequate?
2. Risk Assessment
Identify potential risks:
- Breaking changes that might affect existing functionality
- Database migration requirements
- Performance impact on large datasets
- Compatibility issues with external integrations
3. Recommendations
Provide specific, actionable recommendations:
- Code improvements and refactoring suggestions
- Missing tests or documentation
- Performance optimizations
- Security enhancements
4. Approval Decision
Based on the analysis, provide one of:
- APPROVED - Ready to merge
- � APPROVED WITH MINOR CHANGES - Can merge after addressing minor issues
- L NEEDS WORK - Requires significant changes before merge
Include a summary of the most critical issues that must be addressed before merging.
This review should focus on maintainability, security, performance, and adherence to the Symfony best practices.
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.
- 4d ago First seen · 57 lines · 0 tokens per session scan A f3ded1d59137
pre-commit-review is a command published in the GitHub repository klapaudius/symfony-mcp-server (32 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
10-optimization-finalization
Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.
git
Git operations with intelligent commit messages and workflow optimization.
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.