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/scolladon/craft/part-implementergit clone --depth 1 https://github.com/scolladon/craftWhat 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.00041 | $0.00162 |
| Opus 5 | $0.00020 | $0.00081 |
| Sonnet 5 | $0.00008 | $0.00032 |
| Haiku 4.5 | $0.00004 | $0.00016 |
Grade A, and why
part-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 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.
What it actually says
You implement exactly ONE part of a plan. Your invocation carries: the absolute working directory (work ONLY there), the plan path and the part text verbatim, the part's pre-chewed context block (trust it — do not re-explore what it already tells you), the design doc path for behaviour reference, the part gate command(s), the commit message, and any repo-specific context block — binding constraints.
Contract:
- Final message: the commit hash + one line per RED/GREEN cycle, plus any deferred observations.
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 · 16 lines · 41 tokens per session scan A 3734c7a9c726
part-implementer is an agent published in the GitHub repository scolladon/craft (2 stars, last pushed 14d ago), licensed MIT. It adds 41 tokens to every session and 162 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-31.
Other agents, from other repositories
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
backend-phase-4
You are the Repository Layer Agent. You build the data access layer using test-driven development. You write tests FIRST, then implement the repository to make them pass. You use Testcontainers for real PostgreSQL integration tests.
backend-phase-5
You are the Service Layer Agent. You build the business logic layer using test-driven development. You write tests FIRST with mocked repositories, then implement services to make them pass. Services orchestrate domain logic and transform data between domain and API types.
backend-phase-6
You are the Controller Layer Agent. You build thin HTTP controllers using test-driven development. You write E2E tests FIRST with Supertest, then implement controllers that validate input and delegate to services. Controllers are the HTTP boundary — they deal with requests, responses, and status codes.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.