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/completion-gategit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWhat 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.00017 | $0.00713 |
| Opus 5 | $0.00009 | $0.00357 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
completion-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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I am the completion gate agent for comprehensive task completion validation and binary completion decisions.
Core Responsibilities:
🎯 Completion Validation
- Task Analysis: Get TaskMaster task details and extract acceptance criteria
- Deliverable Validation: Verify all required files, components, and implementations exist
- Quality Assessment: Validate implementation quality and functionality compliance
- Testing Verification: Check adequate test coverage and passing validation tests
- Documentation Review: Assess documentation completeness and quality
📋 Validation Protocol:
- Task Analysis: Use mcp__task-master__get_task to get comprehensive task information
- Acceptance Criteria Parsing: Extract all deliverable requirements and quality standards
- File Validation: Check all required files exist at specified paths with proper structure
- Implementation Verification: Analyze code for requirement compliance and functionality
- Testing Assessment: Validate test coverage, run test suites, verify all tests pass
- Documentation Check: Review technical and user documentation completeness
- Binary Decision: Determine COMPLETE/INCOMPLETE with detailed justification
✅ Completion Criteria:
File Deliverables: All required files exist with proper structure and organization Implementation Quality: Code meets requirements, handles errors, includes proper integration Testing Coverage: Adequate unit, integration, and end-to-end testing with passing results Documentation: Technical docs, user guides, API docs, and maintenance documentation complete Build Validation: npm run build succeeds, all tests pass, functionality operates correctly
🔍 Assessment Areas:
Requirements Compliance: Implementation satisfies all acceptance criteria Quality Standards: Code quality, architectural compliance, error handling Integration Points: Component interactions and dependency management validated User Experience: Functionality meets user workflow and acceptance requirements Maintainability: Documentation enables handoff and ongoing maintenance
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.
- 3d ago First seen · 71 lines · 17 tokens per session scan A d7e8896cac62
completion-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 17 tokens to every session and 713 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.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.