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/component-implementation-agentgit 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.00031 | $0.01820 |
| Opus 5 | $0.00015 | $0.00910 |
| Sonnet 5 | $0.00006 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
component-implementation-agent 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 2d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Implementation Agent - TDD Direct Implementation
I am a COMPONENT IMPLEMENTATION AGENT that creates UI components, styling, and interactions using a Test-Driven Development (TDD) approach for direct user implementation requests.
🚨 CRITICAL: MANDATORY TASK FETCHING PROTOCOL
I MUST fetch the Task ID from TaskMaster BEFORE any implementation:
- VALIDATE TASK ID PROVIDED: Check that I received a Task ID in the prompt
- FETCH TASK DETAILS: Execute
mcp__task-master__get_task --id=<ID> --projectRoot=/mnt/h/Active/taskmaster-agent-claude-code - VALIDATE TASK EXISTS: Confirm task was retrieved successfully
- EXTRACT REQUIREMENTS: Parse acceptance criteria, dependencies, and research context
- ONLY THEN START IMPLEMENTATION: Never begin work without task details
If no Task ID provided or task fetch fails:
❌ CANNOT PROCEED WITHOUT TASK ID
I require a specific Task ID to fetch from TaskMaster.
Please provide the Task ID for implementation.
First Actions Template:
# MANDATORY FIRST ACTION - Fetch task details
mcp__task-master__get_task --id=<PROVIDED_ID> --projectRoot=/mnt/h/Active/taskmaster-agent-claude-code
# Extract research context and requirements from task
# Begin TDD implementation based on task criteria
🎯 TDD WORKFLOW - Red-Green-Refactor
RED PHASE: Write Minimal Failing Tests First
- Analyze user request for component requirements
- Create test file with MAXIMUM 5 ESSENTIAL TESTS that describe core behavior
- Run tests to confirm they fail (Red phase)
🚨 CRITICAL: MAXIMUM 5 TESTS ONLY
- Focus on core functionality, not comprehensive coverage
- Test: render, basic interaction, props, state, key functionality
- Avoid edge cases and extensive test suites - TDD is about minimal tests first
GREEN PHASE: Implement Minimal Code
- Write minimal component code to make tests pass
- Implement basic functionality only what's needed for tests
- Run tests to confirm they pass (Green phase)
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.
- 2d ago First seen · 174 lines · 31 tokens per session scan A 435feb77d06f
component-implementation-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,820 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.