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 skills add ayberkcansever/ai-skills --skill write-plangit clone --depth 1 https://github.com/ayberkcansever/ai-skillsWrote 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/ayberkcansever/ai-skills/write-plan)<a href="https://agentmods.dev/skills/ayberkcansever/ai-skills/write-plan"><img src="https://agentmods.dev/badge/skills/ayberkcansever/ai-skills/write-plan/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/ayberkcansever/ai-skills/write-plan"><img src="https://agentmods.dev/badge/skills/ayberkcansever/ai-skills/write-plan.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.00070 | $0.04547 |
| Opus 5 | $0.00035 | $0.02273 |
| Sonnet 5 | $0.00014 | $0.00909 |
| Haiku 4.5 | $0.00007 | $0.00455 |
Grade A, and why
write-plan 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 8d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Plan
Overview
Write comprehensive implementation plans assuming the engineer has zero context for the codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about the toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the write-plan skill to create the implementation plan."
Context: Plans are written in the user's checkout; they are executed in this checkout if already on the ticket branch, otherwise in a per-ticket worktree that execute-plan opens via the git-worktrees skill. Keep every path in the plan repo-relative so it resolves in either place.
Documentation layout (two tiers)
| Tier | Path | Git | Use |
|---|---|---|---|
| Durable | docs/features/<TICKET-ID>/ |
tracked | Design, implementation plans, test checklists — commit when stable |
| WIP | docs/plans/<TICKET-ID>/ |
gitignored | Agent scratch during write-plan / execute-plan |
Infer <TICKET-ID> from the branch name (e.g. PROJ-123) or ask once if unclear. If your project does not use ticket IDs, use a short kebab-case slug for the feature.
Save new implementation plans to (WIP):
docs/plans/<TICKET-ID>/<scope>-implementation-plan.md
Overwrite guard: if the target plan file already exists, do not rewrite it silently — it may already be audited (interview-plan) or partially executed (ticked checkboxes). Confirm with the user before replacing; prefer amending the existing plan.
Examples:
docs/plans/PROJ-123/backend-implementation-plan.mddocs/plans/PROJ-123/service-implementation-plan.md
Canonical filenames when promoting to docs/features/<TICKET-ID>/:
README.md— index, status, cross-repo linksdesign.md— architecture + decisionsbackend-implementation-plan.md/service-implementation-plan.md/frontend-implementation-plan.mdtest-checklist.html— optional manual QA
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.
- 8d ago First seen · 314 lines · 70 tokens per session scan A b85e0aa9494b
write-plan is a skill published in the GitHub repository ayberkcansever/ai-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 4,547 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-08-31.
Other skills, from other repositories
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
ijfw-tdd
RED-GREEN-REFACTOR enforcement. Use when implementing a feature or bugfix before writing implementation code. Trigger: tdd, test first, red green refactor, /ijfw-tdd.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
go
Go phase. Reads the approved SPEC file, maps Requirements to tasks (plan), executes via TDD (build), and integrates results verifying all Acceptance Criteria.
rpi-remediate
Validate and resolve every actionable pre-launch finding in ordered local waves with TDD, finding disposition and preservation of strategic exceptions.
tdd
Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.