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/clchinkc/document-mcp/9-comprehensive-qagit clone --depth 1 https://github.com/clchinkc/document-mcpWrote 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/clchinkc/document-mcp/9-comprehensive-qa)<a href="https://agentmods.dev/commands/clchinkc/document-mcp/9-comprehensive-qa"><img src="https://agentmods.dev/badge/commands/clchinkc/document-mcp/9-comprehensive-qa.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.00602 |
| Opus 5 | $0.00000 | $0.00301 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
9-comprehensive-qa 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Quality Assurance & Testing
Systematic Quality Improvement: Root cause investigation, comprehensive testing, and continuous quality enhancement using specialized agents.
Phase 1: Quality Assessment & Issue Detection
Use specialized agents (qa-engineer, test-writer-fixer, security-auditor, debug-analyzer) to:
Testing Infrastructure Review:
- Run all test suites (unit, integration, e2e, evaluation, performance, linting, type checking)
- Identify test failures, warnings, errors, and coverage gaps
- Analyze test reliability, performance, and maintenance overhead
- Review testing frameworks compatibility and optimization opportunities
Code Quality Analysis:
- Detect premature optimization, overly complex configuration, unnecessary workarounds
- Identify implementation gaps, immature patterns, and technical debt
- Review error handling, logging, monitoring, and debugging capabilities
- Assess security vulnerabilities, privacy compliance, and data protection
System Reliability Evaluation:
- Analyze system stability, performance bottlenecks, and scalability limits
- Review deployment processes, CI/CD pipelines, and automation effectiveness
- Evaluate monitoring, alerting, and incident response capabilities
- Assess backward compatibility and breaking change management
Phase 2: Root Cause Investigation & Planning
Multi-Agent Round Robin Discussion:
- QA Engineer: Quality standards, testing strategies, and defect analysis
- Security Auditor: Security vulnerabilities and compliance requirements
- Performance Optimizer: Performance bottlenecks and optimization opportunities
- Debug Analyzer: Error patterns, logging effectiveness, and troubleshooting
- Test Writer/Fixer: Test coverage, reliability, and automation improvements
Investigation Requirements:
- Investigate, search, think, and identify root causes for all failures
- Avoid fallback/workaround solutions that mask underlying issues
- Plan modifications to implementation and testing code
- Ensure no regression on existing functionality and progress
- Prioritize fixes that maintain low complexity and clean architecture
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 · 60 lines · 0 tokens per session scan A 59c2ec1f37cc
9-comprehensive-qa is a command published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 602 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-31.
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.
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.