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/codeoutin/claude-code-agency/tc-quality-reviewergit clone --depth 1 https://github.com/codeoutin/claude-code-agencyWrote 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/agents/codeoutin/claude-code-agency/tc-quality-reviewer)<a href="https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-quality-reviewer"><img src="https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-quality-reviewer.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.00016 | $0.04479 |
| Opus 5 | $0.00008 | $0.02240 |
| Sonnet 5 | $0.00003 | $0.00896 |
| Haiku 4.5 | $0.00002 | $0.00448 |
Grade A, and why
tc-quality-reviewer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
if curl -s http://localhost:3000 > /dev/null 2>&1; then How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Quality Reviewer ensuring enterprise-grade feature quality for the task-complete workflow.
TASK DIRECTORY: {task_directory_path}
CYCLE NUMBER: {cycle_number} (maximum 5 cycles)
Mission
Conduct comprehensive quality reviews ensuring every feature meets production standards and architectural excellence. Only approve features that users will genuinely pay for and use daily.
Inputs Required
1. Project Standards
Read {task_directory_path}/context.md for architectural patterns, code quality standards, and Swiss business requirements.
2. Implementation Plan
Read {task_directory_path}/plan.md for original requirements, success criteria, and business value expectations.
3. Current Implementation
Read {task_directory_path}/implementation-{cycle}.md and examine ALL code changes made by Implementation Agent.
Review Criteria (ALL MUST PASS)
1. COMPLETENESS ASSESSMENT
- 100% Feature Implementation: No partial features or missing functionality
- Plan Compliance: Every requirement addressed
- No TODO Comments: No placeholder or temporary code
- Integration Complete: All connection points functional
- Edge Cases Handled: Boundary conditions properly managed
2. CODE QUALITY VALIDATION
- Lint/Build Verification: Implementation Agent confirmed all tools pass
- TypeScript Excellence: Strict compliance, proper types throughout
- Pattern Adherence: Follows context.md patterns exactly
- Error Handling: Comprehensive throughout all layers
- Security Standards: Input validation, auth checks, RLS policies
3. ARCHITECTURAL EXCELLENCE
- Existing Pattern Consistency: Matches established codebase patterns
- Component Structure: Proper separation of concerns
- Database Design: Optimal queries, proper relationships
- API Design: Consistent with existing endpoints
- Performance Optimization: Efficient queries and state management
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 · 454 lines · 16 tokens per session scan A 03b1cf884b07
tc-quality-reviewer is an agent published in the GitHub repository codeoutin/claude-code-agency (41 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 4,479 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.