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 laurigates/claude-plugins --skill blueprint-work-ordergit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/blueprint-work-order)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-work-order"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-work-order/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/laurigates/claude-plugins/blueprint-work-order"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-work-order.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.02557 |
| Opus 5.5 | $0.00016 | $0.01023 |
| Sonnet 5.5 | $0.00008 | $0.00511 |
| Haiku 4.5 | $0.00004 | $0.00256 |
Grade A, and why
blueprint-work-order 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 15d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a work-order document for isolated subagent execution with optional GitHub issue integration.
When to Use This Skill
| Use this skill when... | Use blueprint-prp-create instead when... |
|---|---|
| You're breaking a PRP into delegatable subagent tasks | You're creating the PRP itself with full research and validation gates |
| You want a focused TDD task packet with minimal context | You need a comprehensive context-gathered implementation plan |
You want to spawn a work-order from an existing PRP (--from-prp) |
Use blueprint-prp-execute instead when running an already-written PRP |
You're creating a work-order from a GitHub issue (--from-issue) |
Use confidence-scoring instead to evaluate readiness before delegating |
Flags
| Flag | Description |
|---|---|
--no-publish |
Create local work-order only, skip GitHub issue creation |
--from-issue N |
Create work-order from existing GitHub issue #N (a work-order-draft proposal issue is promoted: packet consumed, label swapped to work-order) |
--from-prp NAME |
Create work-order from existing PRP (auto-populates context) |
Default behavior: Creates both local work-order AND GitHub issue with work-order label.
Interaction Mode
Before any closing AskUserQuestion menu, resolve the automation config:
bash "${CLAUDE_SKILL_DIR}/../../scripts/get-automation-config.sh"
When EFFECTIVE_INTERACTION_MODE=quiet and this invocation was
automation-initiated (autopilot, session bookend, drift-nudge follow-up — not
a slash command the user typed), skip closing navigation menus ("what next?" /
"create another?" style): apply the safe default and end with a one-line
receipt instead. Quiet mode never skips confirmation gates that guard writes —
only navigation menus. A direct user invocation always behaves fully
interactively (explicit intent overrides quiet; see ADR-0020).
Prerequisites
- Blueprint Development initialized (
docs/blueprint/exists) - At least one PRD exists (unless using
--from-issueor--from-prp) ghCLI authenticated (unless using--no-publish)
What ships with it
5 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.
- 15d ago Changed · +9 lines 529618497e88
- 18d ago Changed · -172 lines e111b5d9b4ce
- 1mo ago First seen · 422 lines · 39 tokens per session scan A a8ad0885bdbe
blueprint-work-order is a skill published in the GitHub repository laurigates/claude-plugins (59 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,557 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
delegation-brief
Before delegatetask: brief the subagent, then verify it.
work-ledger
Multi-day or multi-session work: a ledger that survives.
ticket-delivery
End-to-end ticket workflow from analysis through investigation, planning, TDD implementation, commits, and PR creation, adapted to your setup by saved config. Use when starting work on a ticket or implementing a feature from ticket to PR.
backlog-compiler
Converts a PRD, ticket, or feature description into a .code-virtuoso/loop/backlog.json plan sized and ordered for autonomous loop execution. Use when preparing work for the iteration-loop skill, turning a written ticket into a loop-ready backlog, or when asked to turn a spec into a backlog.
morning-brief
Operator's read-only morning view of the current GitHub repo in one pass: open counts per queue label, merge-ready PRs, parked decisions with their RECOMMENDED lines, loop-lane telemetry freshness, per CI lane the week's failures by class, limit stops, restarts and turn headroom, and model usage per activity and…
spec-driven-development
Turns an approved idea or ticket into spec, plan, and task files saved in the repo, then executes them one task at a time with a progress log. Use to write a spec, plan a feature, break work into tasks, or resume multi-session work.