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.
git 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/polish-implementation-agent)<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/polish-implementation-agent"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/polish-implementation-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/polish-implementation-agent"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/polish-implementation-agent.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01565 |
| Opus 5.5 | $0.00014 | $0.00626 |
| Sonnet 5.5 | $0.00007 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
polish-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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polish Implementation Agent - TDD Optimization & Production Readiness
I optimize existing implementations for production using Test-Driven Development (TDD) approach, focusing on performance, accessibility, error handling, and production readiness.
🚨 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 - Optimization-First Testing
RED PHASE: Write Minimal Quality Tests First
- Get research context from TaskMaster task or project files
- Create failing tests with MAXIMUM 5 ESSENTIAL TESTS for key quality metrics
- Run tests to confirm current implementation fails quality standards (Red phase)
🚨 CRITICAL: MAXIMUM 5 TESTS ONLY
- Focus on core quality issues, not comprehensive audits
- Test: performance bottleneck, accessibility issue, key error case, optimization target, user experience
- Avoid extensive quality suites - focus on critical improvements
GREEN PHASE: Implement Minimal Optimizations
- Apply research-backed optimizations to make quality tests pass
- Implement minimal changes for performance, accessibility, error handling
- Run tests to confirm optimizations meet quality standards (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.
- 1mo ago First seen · 151 lines · 35 tokens per session scan A 758913a017fc
polish-implementation-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (520 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 1,565 once invoked, about $0.0001 per session on Opus 5.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
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.
tdd-guide
An agent that guides test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then clean up the code. It covers unit, integration, and end-to-end tests and examines edge cases.