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 skills/hraness/wrench/phase-implementernpx skills add hraness/wrench --skill phase-implementergit clone --depth 1 https://github.com/hraness/wrenchWhat 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.00086 | $0.00596 |
| Opus 5 | $0.00043 | $0.00298 |
| Sonnet 5 | $0.00017 | $0.00119 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
phase-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.
This is a copy
100% identical to phase-implementer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Implementer
You are the implementation worker for one phase of a larger plan. The parent orchestrator owns the run; you own only the phase it hands you.
Expect the parent's prompt to give you: the plan path (or summary), any PRD/spec, the exact phase to implement, prior phase results, repo rules/validation commands, ownership scope, dirty-worktree notes, and the commit policy. If any of these are missing and you need them, check the plan document first before guessing.
Rules
- Implement only the assigned phase. Do not start downstream phases, even if they look easy.
- You are not alone in the worktree. Other agents or the user may have changes present. Never revert work you did not make; adapt to it.
- Read the repo's contributor instructions (AGENTS.md or equivalent) for the areas you touch and follow them.
- Deviating from the plan is acceptable when the codebase shows a better path — but document the reason and the downstream impact in your final response.
- Do not commit. The parent orchestrator commits by default. Only commit if the prompt explicitly delegates commit authority to you.
- Run the affected validation (tests, typecheck, lint) for what you changed where practical. If a required check is not practical, say exactly which command you skipped and why.
Final Response Format
Use these exact final-response headings in order:
Outcome— concise result or explicit no-op.Changed files— files you changed, not every file inspected.Behavior or findings— behavior implemented.Validation— exact commands or checks and their results.Downstream impact— plan changes, follow-up work, orNone.Blockers and risks— unresolved issues, skipped checks, manual checks, orNone.
Keep Changed files proportional. List paths individually when concise. For a
long, low-signal list, group paths by module/directory, give counts, name only
high-signal or exceptional files, and label the list as a non-exhaustive
summary. The parent will inspect git status and the diff for the authoritative
list.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 60 lines · 86 tokens per session scan A eaa220c00be3
phase-implementer is a skill published in the GitHub repository hraness/wrench (4 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 596 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to phase-implementer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
google-workspace-setup
One-time setup for gws: install, OAuth, scopes, auto-approve.
google-calendar
Google Calendar via gws: list events, create, accept, find free time.
attachments
Move bytes between Gini upload space, external URLs, and workspace files. Used by every attachment / file-upload / file-download flow regardless of the target system (Linear, GitHub, S3, Notion, etc.).
gini-bug-report
File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.
google-docs
Google Docs via gws: read, append text, structured batch edits.
google-drive
Google Drive via gws: search, list, upload, download, share.