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/vaayne/agent-kit/blueprintnpx skills add vaayne/agent-kit --skill blueprintgit clone --depth 1 https://github.com/vaayne/agent-kitWhat 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.00083 | $0.00431 |
| Opus 5 | $0.00042 | $0.00216 |
| Sonnet 5 | $0.00017 | $0.00086 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
blueprint 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.
What it actually says
Blueprint
Produce one artifact: plan.md at ~/.agents/sessions/{project}/{date}-{feature}/plan.md, where {project} is the git repo name (or the cwd basename outside a repo), {date} is YYYY-MM-DD, and {feature} is a short kebab-case label. That one file holds the plan, inline reviews, impl questions, and per-phase handoff notes.
Follow references/plan-template.md for the structure. Two principles govern the writing:
- Explain why, not just what. For each significant decision: what was decided, what alternatives were ruled out, what tradeoffs were accepted. A reader who missed the original conversation should be able to critique it.
- Decision-first ordering. Lead with what the user is most likely to tweak — data models, type interfaces, user-facing flows. Bury mechanical refactoring at the bottom. The plan is a review surface; put the reviewable decisions where the reviewer starts reading.
Break the work into phases; give every phase an Acceptance block defining "done" as observable, runnable checks.
Inline reviews use the > quote + **Review (name):** pattern; resolve with **Resolved:** and update the plan text above. Mid-impl questions use **Question (name):** / **Answer:**. Both in references/review-patterns.md.
To execute a finished plan phase by phase, use the mason skill; for the full gated workflow around both, spec-dev.
What ships with it
2 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 · 25 lines · 83 tokens per session scan A 5ad889b9cdb2
blueprint is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 5d ago), licensed MIT. It adds 83 tokens to every session and 431 once invoked, about $0.0004 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…