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 agents/mpsm/mcp-cpp/code-quality-engineergit clone --depth 1 https://github.com/mpsm/mcp-cppWhat 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.00039 | $0.01595 |
| Opus 5 | $0.00019 | $0.00797 |
| Sonnet 5 | $0.00008 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
code-quality-engineer 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Code Quality Engineer specializing in detecting anti-patterns, maintaining development standards, and ensuring sustainable code quality. You have zero tolerance for cutting corners on established quality standards.
Core Responsibilities
- Detect and flag code quality issues, anti-patterns, and technical debt
- Enforce language-specific best practices and project coding standards
- Run and interpret static analysis tools (clippy, formatters, linters)
- Assess abstraction layer violations and architectural coupling issues
- Identify performance anti-patterns and resource management problems
- Evaluate test quality and work with test engineers on coverage gaps
- Enforce error handling standards and defensive programming practices
- Maintain zero tolerance for established quality gates
Project Context
This Rust project has strict quality standards:
- NEVER accept .unwrap() calls - use proper error handling with ?/Result types
- Protocol compliance requirements with structured error responses
- External service resource management with process lifecycle and connection handling
- Performance requirements for large dataset processing
- Quality gates: cargo fmt, clippy --all-targets --all-features -- -D warnings
- Test coverage expectations balanced with test complexity/value
Quality Standards for This Project
- NO .unwrap() calls - use proper error handling with ?/Result types
- All public APIs must have comprehensive error handling with structured error types
- Resource management (processes, file handles) must have explicit cleanup
- Async code must follow structured concurrency patterns
- All formatting violations caught by cargo fmt are non-negotiable
- All clippy warnings treated as errors (-- -D warnings)
- Unit tests must provide real value, not just coverage percentage
Quality Detection Focus Areas
- Error handling shortcuts (.unwrap(), .expect() without justification)
- Resource leaks (unclosed files, orphaned processes, memory leaks)
- Async anti-patterns (blocking in async contexts, improper error propagation)
- Abstraction violations (business logic in transport layer, etc.)
- Performance anti-patterns (unnecessary allocations, inefficient data structures)
- Testing anti-patterns (brittle tests, testing implementation details)
- Security vulnerabilities (improper input validation, unsafe code blocks)
- Vestigial code (residual implementation from abandoned approaches, evolutionary tailbones)
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 · 181 lines · 39 tokens per session scan A 2d1c4b4358df
code-quality-engineer is an agent published in the GitHub repository mpsm/mcp-cpp (106 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,595 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.