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/feo2x/guided-coding/guided-coding-write-plannpx skills add feO2x/guided-coding --skill guided-coding-write-plangit clone --depth 1 https://github.com/feO2x/guided-codingWhat 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.00031 | $0.00688 |
| Opus 5 | $0.00015 | $0.00344 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
guided-coding-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 yesterday.
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
91% identical to write-plan — 7 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a Plan
Write the agreed approach into ai-plans/. Do not use this skill to begin or replace the
planning conversation. Read the repository instructions, including ai-plans/AGENTS.md, first.
After writing, report the plan path and stop.
File name
Use:
YYYY-MM-DD-HHMM-<issue-id>-<kebab-case-description>.md
Omit <issue-id>- when the work has no tracker issue. Obtain the current UTC timestamp from the
shell; never infer it from conversation context. For example:
date -u +%F-%H%M
In PowerShell, use (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd-HHmm").
Normalize the tracker identifier for filenames: convert it to lowercase, remove a leading #,
replace each run of characters other than a-z and 0-9 with one hyphen, trim leading and trailing
hyphens, and do not add zero padding. Stop if normalization produces an empty identifier. If the
work requires an issue but none exists, stop and suggest the Guided Coding issue-preparation skill
instead of creating a temporary filename.
Resolve the complete destination path before writing and confirm it does not exist. Never overwrite or reuse an existing plan or Plan Deviations document; report a collision and stop.
Structure
Start with # Title, followed by exactly these ## sections in order:
## Rationale: briefly state the problem and overarching goal.## Acceptance Criteria: list observable, verifiable outcomes as unticked Markdown tasks (- [ ]). Describe results, not implementation steps.## Technical Details: record important decisions, constraints, affected components, and non-obvious interactions. Give a senior engineer room to implement.
Use minimal code examples only when they clarify an important contract, such as an API signature, interface, or DTO shape. Say whether an example is exact or illustrative when unclear. Avoid method bodies, step-by-step instructions, exhaustive file lists, and routine background.
When behavior changes, require appropriate automated test coverage in the acceptance criteria. Require benchmarks only when performance is a material risk or requirement.
What ships with it
1 file 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.
- yesterday First seen · 77 lines · 31 tokens per session scan A 7a8c8ac45209
guided-coding-write-plan is a skill published in the GitHub repository feO2x/guided-coding (6 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 688 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to write-plan, differing in 7 lines, and is treated as a copy.
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…