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 XRenSiu/claude-code-forge --skill writing-plansgit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/writing-plans)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/writing-plans"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/writing-plans/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/xrensiu/claude-code-forge/writing-plans"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/writing-plans.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.00000 | $0.01604 |
| Opus 5.5 | $0.00000 | $0.00642 |
| Sonnet 5.5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
writing-plans 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Core Principle: Plans should be executable by someone with "zero project context, poor judgment, and an aversion to writing tests."
Announce at start: "I'm using the writing-plans skill to create a detailed implementation plan."
When to Use
- Before implementing any feature with more than one file change
- When PRD or design is approved and ready for execution
- When breaking down complex work for subagent execution
- When handoff to another engineer/session is needed
The 2-5 Minute Rule
Every task must be completable in 2-5 minutes.
This is the most important constraint. If a task takes longer, it's not detailed enough.
digraph task_sizing {
"Task Idea" -> "Can complete in 2-5 min?" [shape=diamond];
"Can complete in 2-5 min?" -> "Good Task" [label="yes"];
"Can complete in 2-5 min?" -> "Break Down Further" [label="no"];
"Break Down Further" -> "Task Idea";
}
What Makes a Good Task
✅ Must Have
| Element | Bad Example | Good Example |
|---|---|---|
| Precise File Path | "Update the user module" | src/models/user.ts |
| Complete Code | "Add validation" | Full function with all validation logic |
| Verification | "Make sure it works" | npm test -- --grep "User.validate" |
| Estimate | "Shouldn't take long" | "3 min" |
| Dependencies | "After the other stuff" | "Depends on: T001, T002" |
❌ Red Flags in Task Descriptions
These phrases indicate the task is too vague:
| Red Flag Phrase | Problem | Fix |
|---|---|---|
| "Add appropriate validation" | What validation? | List every validation rule with code |
| "Handle errors gracefully" | How exactly? | Show the try/catch with specific errors |
| "Follow existing patterns" | Which pattern? | Paste the actual pattern code |
| "Similar to X" | Different how? | Show the adapted code |
| "Update as needed" | Ambiguous | List every update explicitly |
| "Implement the rest" | Undefined scope | Enumerate every item |
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.
- 1mo ago First seen · 247 lines · 0 tokens per session scan A 98310d72be24
writing-plans is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,604 tokens. 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-09-05.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…