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/djscheuf/agentic-dev-ecosystem-template/draft-implementation-plannpx skills add djscheuf/agentic-dev-ecosystem-template --skill draft-implementation-plangit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWhat 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.00018 | $0.00537 |
| Opus 5 | $0.00009 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
draft-implementation-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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steps:
1. Read the Story Analysis Document
- Read the story analysis json document.
2. Create Plan JSON File
- create a new json file in the same directory as the extracted intent json document, using the same filename but with the suffix
.plan.json. e.g. "create-object-with-validation.plan.json" - The json will follow
/schema/plan.schema.json. - set the source_story to the file path of the story analysis json document.
3. Identify the Workstreams
- Review the Repository, and identify the key application layers such as UI, API, Database, External Services, etc.
- Identify the layers and components that will be affected by this implementation.
- populate the "impacted_layers" field in the plan json file.
4. Draft Implementation Plan
Outline high-level approach, and the layer each of the steps belong to:
IMPLEMENTATION PLAN:
1. [First major step]
2. [Second major step]
3. [Third major step]
...
Update the "steps" field in the plan json file.
5. Draft Testing Strategy
Outline the testing strategy, and the layer each of the test belong to, based on the AC:
TESTING STRATEGY:
├── Unit tests: [Key behaviors to test]
├── Integration tests: [System interactions]
└── E2E tests: [User scenarios]
Update the "testing_strategy" field in the plan json file.
6. Draft Risks and Mitigations
Outline the risks and mitigations, and the layer each of the mitigation would be applied in:
RISKS AND MITIGATIONS:
├── Risk 1: [Description]
│ └── Mitigation: [Approach]
└── Risk 2: [Description]
└── Mitigation: [Approach]
Update the "risks_and_mitigations" field in the plan json file.
7. Write the Sentinel File
- create a sentinel file in the
.processdirectory, named{skill-name}.done.json. - the sentinel file will follow @/schema/sentinel.schema.json.
- set the task field to "{skill-name}".
- the verify_params of the sentinel file will follow @/schema/verify-params.schema.json.
- set the verify_params as follows:
- set "plan_path" as the path to the plan file relative to repo root.
What ships with it
4 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 · 69 lines · 18 tokens per session scan A 942a507e0cdb
draft-implementation-plan is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 537 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…