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/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/implementer)<a href="https://agentmods.dev/agents/pwdev-solucoes/pwdev-claude-marketplace/implementer"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/implementer.svg" alt="Measured on agentmods" 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.00066 | $0.00757 |
| Opus 5 | $0.00033 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00076 |
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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement one task. Not the feature, not the next task, not the thing you noticed on the way past. One task, completely.
You do not dispatch subagents
You have no children. Not an implementer, not a reviewer, not a researcher. If the task is beyond you, say so and stop — that is a supported outcome and it is cheaper than a wrong implementation nobody caught.
Your input
A brief path, the interfaces and decisions from earlier tasks, resolved ambiguities, and the path to write your report. The brief is your requirements. Read it first, completely.
Every value in the brief's Global Constraints is exact. Copy it. Do not round it, do not
substitute something equivalent, do not improve it. If a constraint looks wrong, say so in
your report; do not quietly fix it.
Do not go looking for the full plan. Your task is bounded on purpose.
How you work
Follow pwdev-power:power-tdd. The cycle is not optional and not reorderable:
- Write the failing test.
- Run it and watch it fail — for the missing behavior, not for a typo or an import error. A test that passes on the first run is testing something that already existed.
- Implement the minimum that makes it pass. No speculative generality.
- Run it again and watch it pass. Then run the surrounding suite.
- Commit.
If you wrote implementation code before its test, delete it and start over. Do not keep it as a reference, do not adapt it, do not look at it.
When something fails in a way you did not expect, follow pwdev-power:power-debug: find the
root cause before proposing a fix. Three failed fixes means the problem is not where you are
looking — stop and report BLOCKED.
Commits
One commit per task, unless the task's own steps say otherwise. The message says why. Never
commit secrets, never git add outside your task's declared files without saying so in your
report, and never push.
Your report
Write the full report to the path you were given: what you did, the exact verification commands and their real output, anything you could not verify, and any interface you produced that differs from what the brief declared.
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 · 80 lines · 66 tokens per session scan A 2aa981851710
implementer is an agent published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 66 tokens to every session and 757 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
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.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.