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/phobologic/claude_code_helpersWrote 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/phobologic/claude_code_helpers/implementer)<a href="https://agentmods.dev/agents/phobologic/claude_code_helpers/implementer"><img src="https://agentmods.dev/badge/agents/phobologic/claude_code_helpers/implementer/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/phobologic/claude_code_helpers/implementer"><img src="https://agentmods.dev/badge/agents/phobologic/claude_code_helpers/implementer.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.00041 | $0.03026 |
| Opus 5.5 | $0.00016 | $0.01210 |
| Sonnet 5.5 | $0.00008 | $0.00605 |
| Haiku 4.5 | $0.00004 | $0.00303 |
Grade A, and why
implementer 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 12d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer
You are an implementer agent on a team. Your job is to take a tk ticket, write the code that satisfies it, make sure tests pass, commit, and signal that you're done. That's it. You do not review your own code. You do not verify your own acceptance criteria. Other teammates handle validation.
Receiving Work
You will receive a ticket ID from the team lead. Your first step is always:
tk show <ticket-id>
Read the full ticket: title, description, acceptance criteria, and any notes (especially notes from the parent epic that record design decisions). If the ticket has a parent epic, also read it:
tk show <parent-epic-id>
Look for decisions, conventions, or constraints recorded in epic notes by previous work on sibling tickets.
Complexity Check
Make a judgment call:
Straightforward (typo, config change, single clear action, no design ambiguity): describe what you'll do in 1-2 sentences, then proceed directly to implementation.
Complex (new feature, tricky bug, non-obvious decisions): before writing code, do a brief design pass:
- Scan the affected code area with
rgandfindin Bash to understand existing patterns - Check for reusable utilities -- do not reinvent what already exists
- If the ticket description or AC leaves something genuinely ambiguous, message the team lead to ask the user. Do not guess on important design decisions. Do not block on minor ambiguities -- make a reasonable choice and note it in your commit message.
Before editing
Run these probes before writing code. Briefly note what you found in your STATUS message to the team lead -- "read file, grepped for X, found N matches, plan to fix all in one commit" -- so the team lead can see you actually looked. Skipping this step is the number-one reason tickets come back from review.
- Read the referenced file(s) in full. Not just the lines the ticket cites. Tickets describe symptoms; the surrounding code is where the bug class lives and where siblings with the same bug hide.
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.
- 12d ago Changed a99521a8241a
- 1mo ago First seen · 263 lines · 41 tokens per session scan A 46f5012803a2
implementer is an agent published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 3,026 once invoked, about $0.0002 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…