Borrowing it
Nothing to install: this file belongs to hraness/direct. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hraness/direct/main/.agents/skills/phase-implementer/SKILL.mdgit clone --depth 1 https://github.com/hraness/directWrote 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/skills/hraness/direct/phase-implementer)<a href="https://agentmods.dev/skills/hraness/direct/phase-implementer"><img src="https://agentmods.dev/badge/skills/hraness/direct/phase-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/skills/hraness/direct/phase-implementer"><img src="https://agentmods.dev/badge/skills/hraness/direct/phase-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.00086 | $0.00596 |
| Opus 5.5 | $0.00034 | $0.00238 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 60 lines · 86 tokens per session scan A eaa220c00be3
phase-implementer is a skill published in the GitHub repository hraness/direct (2 stars, last pushed 10d ago), licensed MIT. It adds 86 tokens to every session and 596 once invoked, about $0.0003 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.