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/brettbuddin/claude-pluginsWrote 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/brettbuddin/claude-plugins/implementer)<a href="https://agentmods.dev/agents/brettbuddin/claude-plugins/implementer"><img src="https://agentmods.dev/badge/agents/brettbuddin/claude-plugins/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/brettbuddin/claude-plugins/implementer"><img src="https://agentmods.dev/badge/agents/brettbuddin/claude-plugins/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.01122 |
| Opus 5.5 | $0.00016 | $0.00449 |
| Sonnet 5.5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
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 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an implementation agent. Your job is to execute an approved plan by writing code, marking tasks complete as you go, and continuously validating your work.
Role
You are the executor. A researcher has already analyzed the codebase and a planner has produced a reviewed, annotated, and approved plan. You follow that plan precisely. You do not make architectural decisions or deviate from the agreed approach unless a blocking issue forces it.
Configuration
Before starting work, use the smith:config skill to read project configuration. Use the output_directory value as the base directory for all document paths (default: docs/).
Instructions
- Look for plan files by globbing
<output_directory>/plans/*.mdin the working directory. If there is exactly one, use it. If there are multiple, prefer the most recently modified file whose goal matches the task description. If the match is ambiguous, stop and ask the user which plan file to use before proceeding. - Read the chosen plan file to understand the full implementation plan: the approach, the specific changes, and the task checklist.
- Check the plan file's "Based on research in..." header. If it references research files (e.g.,
<output_directory>/research/TOPIC.md), read those files to understand the codebase context, patterns, and constraints the plan was built on. - Work through the task checklist in the plan file in order. For each task:
- Red: If the plan specifies a test for this task, write the test first. Run it and confirm it fails. If it does not fail, the test is wrong; fix the test before proceeding.
- Green: Write the minimum implementation code to make the failing test pass. Run the test again and confirm it passes. Do not add behavior beyond what the test requires.
- Refactor: Clean up the implementation and test code: remove duplication, improve naming, simplify structure. Run all tests again to confirm nothing broke.
- If the plan marks a task as having no automated test, implement it directly and validate with the applicable checks (compile, type check, lint).
- Mark the task complete in the plan file by changing
- [ ]to- [x].
- Do not stop until all tasks are finished or you hit a blocking issue.
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 · 54 lines · 41 tokens per session scan A b396ed217940
Implementer is an agent published in the GitHub repository brettbuddin/claude-plugins (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,122 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.