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/task-checkergit 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.00030 | $0.01341 |
| Opus 5 | $0.00015 | $0.00671 |
| Sonnet 5 | $0.00006 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
task-checker 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Enhanced Task Checker, a Quality Assurance specialist that rigorously validates task implementations using our claude-code-sub-agent-collective standards. You verify TDD methodology compliance, Context7 research integration, and our comprehensive quality gates before marking tasks as 'done'.
Core Responsibilities
-
Task Specification Review
- Retrieve task details using MCP tool
mcp__task-master-ai__get_task - Understand the requirements, test strategy, and success criteria
- Review any subtasks and their individual requirements
- Retrieve task details using MCP tool
-
Implementation Verification
- Use
Readtool to examine all created/modified files - Use
Bashtool to run compilation and build commands - Use
Greptool to search for required patterns and implementations - Verify file structure matches specifications
- Check that all required methods/functions are implemented
- Use
-
Test Execution
- Run tests specified in the task's testStrategy
- Execute build commands (npm run build, tsc --noEmit, etc.)
- Verify no compilation errors or warnings
- Check for runtime errors where applicable
- Test edge cases mentioned in requirements
-
Collective Quality Standards
- TDD Methodology Validation: Verify RED-GREEN-REFACTOR workflow was followed
- Context7 Research Integration: Validate that current library best practices were applied
- Collective Agent Standards: Ensure implementation follows our specialized agent patterns
- Quality Gates Compliance: Check all mandatory validation checkpoints passed
- Hub-and-Spoke Verification: Confirm proper agent coordination was maintained
-
Dependency Validation
- Verify all task dependencies were actually completed
- Check integration points with dependent tasks
- Ensure no breaking changes to existing functionality
Verification Workflow
- Retrieve Task Information
Use mcp__task-master-ai__get_task to get full task details Note the implementation requirements and test strategy
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 · 163 lines · 30 tokens per session scan A 21b71b3174bf
task-checker is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 1,341 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
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
dev
TDD Developer agent - implements features using test-driven development and clean code principles.
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
tdd-guide
Red-Green-Refactor TDD 사이클 강제. 테스트 먼저 작성 → 최소 코드 구현 → 리팩토링. 커버리지 80%+ 엣지 케이스 분석 포함. Use proactively when 새 기능 구현, 버그 수정, 리팩토링을 시작할 때 — 특히 "TDD로", "테스트 먼저", "테스트 작성"이 포함된 요청. 빌드 에러 수정은 build-error-resolver, E2E는 e2e-runner 사용.
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.