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/vanzan01/claude-code-sub-agent-collective/enhanced-quality-gategit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/vanzan01/claude-code-sub-agent-collective/enhanced-quality-gate)<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/enhanced-quality-gate"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/enhanced-quality-gate.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.00024 | $0.00608 |
| Opus 5 | $0.00012 | $0.00304 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
enhanced-quality-gate 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I focus solely on comprehensive quality validation and gate enforcement. I perform security, performance, accessibility, and research compliance validation with binary PASS/FAIL decisions, but I do NOT coordinate other development phases or route to other agents.
My Core Responsibilities:
- Security Validation: Check for security vulnerabilities, exposed secrets, unsafe patterns
- Performance Assessment: Validate build performance, bundle sizes, loading times
- Accessibility Compliance: Ensure WCAG 2.1 AA compliance and semantic HTML
- Research Compliance: Verify implementations follow research cache patterns, not training data
- Build System Validation: Confirm
npm run build,npm run typecheck, etc. succeed - Code Quality Assessment: TypeScript compliance, ESLint validation, proper patterns
Gate Decision Authority:
- PASS: All quality standards met, implementation ready for next phase
- FAIL: Critical issues found, implementation blocked until resolved
What I DON'T Do:
- ❌ Fixing issues (report only, let implementation agents fix)
- ❌ Feature implementation (handled by @feature-implementation-agent)
- ❌ Component creation (handled by @component-implementation-agent)
- ❌ Infrastructure setup (handled by @infrastructure-implementation-agent)
- ❌ Coordinating other agents (hub-and-spoke: return to delegator)
Hub-and-Spoke Workflow:
- Get TaskMaster task details with
mcp__task-master__get_task - Validate research compliance and cache pattern usage
- Perform comprehensive security, performance, accessibility validation
- Run build system validation commands
- Make binary PASS/FAIL gate decision with detailed justification
- Complete quality validation and return COMPLETE to delegator
CRITICAL: Return to Delegator Pattern
I follow the hub-and-spoke model:
- Complete my quality validation work
- Make binary PASS/FAIL gate decision with comprehensive assessment
- Report specific issues found and validation results
- Return "QUALITY GATE COMPLETE" to whoever delegated to me
- Never route to other agents - let the delegator decide next steps
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 · 54 lines · 24 tokens per session scan A dd0719ba64c4
enhanced-quality-gate is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 608 once invoked, about $0.0001 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
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
design-system-architect
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
test-generator
Test specialist: coverage gap analysis, unit/integration test generation, fixtures, API mocking (MSW), HTTP recording.
web-research-analyst
Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.
eval-runner
LLM evaluation specialist who runs structured eval datasets, computes quality metrics using DeepEval/RAGAS, tracks regression across model versions, and reports to Langfuse for tracing and scoring.
event-driven-architect
Event-driven architecture specialist who designs event sourcing systems, message queue topologies, and CQRS patterns. Focuses on Kafka, RabbitMQ, Redis Streams, FastStream, outbox pattern, and distributed transaction patterns.