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 wiolett-industries/marketplace --skill writing-plansgit clone --depth 1 https://github.com/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/writing-plans)<a href="https://agentmods.dev/skills/wiolett-industries/marketplace/writing-plans"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/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/wiolett-industries/marketplace/writing-plans"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/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.00051 | $0.01017 |
| Opus 5 | $0.00026 | $0.00508 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Create a durable plan only when it materially improves execution or recovery. Plans are source-of-truth artifacts, not mandatory ceremony.
Plan Threshold
Use this module when at least one is true:
- the user explicitly requests a durable implementation plan;
- execution has several dependent steps or independent subsystems;
- risk, migration, coordination, or compaction recovery requires locked decisions;
- another agent must execute without product or architecture guesswork.
Fast localized work and chat-only planning skip .workflow/. An explicit no-edits/read-only boundary blocks plan artifacts unless the user separately authorizes a durable plan.
Planning Does Not Expand Context
A plan is not permission to map or preemptively harden. Every task must trace to stated behavior, observed failure, or normal-path risk. Cut only work outside acceptance, normal flow, integrity/security, and compatibility; minimal means behavior-complete, not partial. Reuse the working set; don't rediscover after create, reflection, or compaction.
Create Or Resume
Use workflow_plan_create, workflow_plan_update, workflow_plan_artifact_write, and workflow_handoff_write when available. Manual .workflow/ writes are fallback only. Resume an unfinished matching run; do not reopen completed work by default.
Read references/plan-schema.md when creating a run, defining chunks/tasks, or writing a plan handoff. Do not load it for a chat-only plan.
Plan Contract
The plan must lock decisions that execution cannot safely infer:
- exact goal, success criteria, scope, and non-goals;
- expected change class (
L0-L3), expected surfaces, must-preserve constraints, and the smallest behavior-complete approach; - repository facts at the known surfaces, constraints, and accepted decisions;
- implementation approach and dependency order;
- tasks with allowed scope, ownership, and expected files/artifacts;
- verification commands and acceptance checks;
- UI contract reference and its reuse decision when substantial production UI is in scope;
- assurance profile, one task-wide agent budget, and finalization requirements.
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.
- 12d ago First seen · 68 lines · 51 tokens per session scan A 1e202faa7ac4
writing-plans is a skill published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 1,017 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…