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/owainlewis/blueprint/plannpx skills add owainlewis/blueprint --skill plangit clone --depth 1 https://github.com/owainlewis/blueprintWrote 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/owainlewis/blueprint/plan)<a href="https://agentmods.dev/skills/owainlewis/blueprint/plan"><img src="https://agentmods.dev/badge/skills/owainlewis/blueprint/plan.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.01106 |
| Opus 5 | $0.00021 | $0.00553 |
| Sonnet 5 | $0.00008 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Create tasks that a new agent can finish without making product or technical decisions. Split work by working result, not by file, layer, or team boundary.
Process
- Read the source, repository instructions, and relevant code.
- Stop and return to design if an unresolved choice would change behavior, interfaces, data, security, scale, performance, compatibility, operations, cost, or proof.
- Split the work into tasks that each deliver working behavior, fit one agent run, and produce one focused pull request.
- Keep shared contracts in one task. Do not make two tasks answer the same question independently.
- Separate refactoring when it would hide a behavior change.
- Order tasks by dependency. Add a milestone only when it creates a useful delivery or review boundary.
- Return the plan in chat. Create tracker tickets only when the user asks. Never write a plan document.
- Stop after planning. Do not implement.
Write for two readers
Each task is read by a human and executed by an agent.
The first sections must let a human understand the task in under a minute. State the concrete problem, the result, and why it matters in everyday words. Do not use requirement IDs, implementation details, undefined project terms, or acronyms unfamiliar to the intended readers there.
Put task-specific decisions, interfaces, failure rules, and security constraints in Agent notes. Link the design or decided source for shared architecture and full requirement definitions. Use a repository path or URL that will resolve from the published ticket, and pin the decided version when later edits could change the contract. If no durable source exists, include the required shared decisions in Agent notes. Do not copy the whole source into every ticket.
A task stands alone when its purpose, boundary, dependencies, non-negotiable decisions, and proof are clear. It does not need to repeat background that the linked source already explains.
Task shape
Use this compact shape. Omit optional sections that add no information.
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.
- 5d ago First seen · 97 lines · 42 tokens per session scan A 3a30f99f8e1e
plan is a skill published in the GitHub repository owainlewis/blueprint (375 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 1,106 once invoked, about $0.0002 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
speckit-prd
Collaboratively turn a raw product or technical idea into three artifacts — a lean PRD, a technical roadmap with a SPEC catalog, and a roadmap-MOC home note — ready for $speckit-scaffold-spec and $speckit-autopilot. Use when the user says: "write a PRD", "$speckit-prd", "create a product requirements document", "draft…
speckit-status
Show the current SpecKit roadmap and workflow status in Codex. Aggregates workflow files and technical roadmaps, highlights active specs, identifies blocked work, and recommends the next unblocked spec to start.
to-issues
Break a plan or PRD into vertical-slice issues on the project issue tracker.
to-prd
Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.
speckit.status
Progress Dashboard - Displays project progress status.
speckit.taskstoissues
Issue Tracker Syncer - Synchronize tasks.md to issue tracker.