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-story-reconcilegit 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-story-reconcile)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-story-reconcile"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-story-reconcile/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-story-reconcile"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-story-reconcile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 9 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00041 | $0.02721 |
| Opus 5 | $0.00020 | $0.01360 |
| Sonnet 5 | $0.00008 | $0.00544 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
blueprint-story-reconcile 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 7d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:story-reconcile
Apply the drift findings from /blueprint:story-audit back to the PRDs. Adds status markers, a Known Drift section, and (with consent) promotes candidate stories. Does not delete unimplemented requirements — they remain the roadmap.
Usage: /blueprint:story-reconcile [--audit <path>] [--prd <path>] [--apply-all] [--dry-run]
When to Use This Skill
| Use this skill when... | Use alternative when... |
|---|---|
| Marking PRD requirements as implemented / partial / missing after an audit | Producing the audit itself (/blueprint:story-audit) |
| Adding a "Known Drift" section to a PRD | Generating PRDs from scratch (/blueprint:derive-plans) |
| Promoting a single candidate story into the PRD with user consent | Bulk-rewriting PRDs (this skill is deliberately conservative) |
This skill only edits PRDs. Code changes belong to /blueprint:work-order. Audit re-runs belong to /blueprint:story-audit.
Context
- Latest audit: !
find . -path '*/docs/blueprint/audits/*' -maxdepth 4 -name '*-story-audit.md' - PRD directory: !
find . -path '*/docs/prds' -maxdepth 2 -type d - PRD files: !
find . -path '*/docs/prds/*' -maxdepth 3 -name '*.md' - Manifest: !
find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' - Branch: !
git branch --show-current - Repo status: !
git status --porcelain=v2 --branch
Parameters
Parse $ARGUMENTS:
--audit <path>: Path to the audit artifact. Default: most-recent file matchingdocs/blueprint/audits/*-story-audit.md(sort lexically — date-stamped names sort correctly).--prd <path>: Limit edits to a single PRD. Default: every PRD referenced by the audit's drift table.--apply-all: Skip per-row prompts and apply every drift entry as an edit. Use only when the audit was reviewed elsewhere.--dry-run: Show the planned edits as unified diffs without writing.
Interaction Mode
Before any closing AskUserQuestion menu, resolve the automation config:
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.
- 7d ago First seen · 234 lines · 41 tokens per session scan A 0a8722255053
blueprint-story-reconcile is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,721 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-09-03.
Other skills, from other repositories
sdlc
Run an artifact-driven software lifecycle where each stage commits a markdown artifact that triggers the next - intent.md, spec.md, plan.md, verified diff, reviewed PR, monitored production. Use when the user asks to capture an idea as intent, write a spec, plan before implementing, set up a verification loop, define…
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
kanban-dev-lane
Use when a Hermes Kanban worker wants to run an autonomous implementation delegation lane with a 3-tier fallback chain across claudy -> codex (--yolo) -> agyd (agy --dangerously-skip-permissions) -> Hermes direct on quota exhaustion.
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
ma
A coordinator for taking a software ticket from requirements through design, implementation, review, and merge request. It uses quality gates, recorded documents, approvals, and validation between stages.