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-auditgit 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-audit)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-story-audit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-story-audit/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-audit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-story-audit.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.00038 | $0.02528 |
| Opus 5.5 | $0.00015 | $0.01011 |
| Sonnet 5.5 | $0.00008 | $0.00506 |
| Haiku 4.5 | $0.00004 | $0.00253 |
Grade A, and why
blueprint-story-audit 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 6d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:story-audit
Reconcile what the codebase actually does against what the PRD says it should do, then map every story to its tests and rank the gaps. Produces one durable artifact: docs/blueprint/audits/<date>-story-audit.md.
Usage: /blueprint:story-audit [--scope <area>] [--prd <path>] [--no-write] [--report-only]
When to Use This Skill
| Use this skill when... | Use alternative when... |
|---|---|
| Auditing PRD↔code drift before a release or planning round | Drafting a brand-new PRD from scratch (/blueprint:derive-plans) |
| Finding untested critical paths through the user-story lens | Mining commits for missing tests (/blueprint:derive-tests) |
| Surfacing "implicit stories" — code-only features missing from PRD | Validating ADR relationships (/blueprint:adr-validate) |
| Producing a single artifact the team can act on top-to-bottom | Listing existing blueprint docs (/blueprint:docs-list) |
This skill is read-only apart from the audit artifact. PRD edits live in /blueprint:story-reconcile; agent dispatch for gap-fill work lives in /blueprint:work-order.
Context
- Blueprint manifest: !
find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' - PRD directory: !
find . -path '*/docs/prds' -maxdepth 2 -type d - PRD files: !
find . -path '*/docs/prds/*' -maxdepth 3 -name '*.md' - Audits directory: !
find . -path '*/docs/blueprint/audits' -maxdepth 3 -type d - Existing audits: !
find . -path '*/docs/blueprint/audits/*' -maxdepth 4 -name '*.md' - Test directories: !
find . -maxdepth 3 -type d \( -name tests -o -name __tests__ -o -name test -o -name spec \) -not -path '*/node_modules/*' - Repo root: !
git rev-parse --show-toplevel - Today: !
date -u +%Y-%m-%d
Parameters
Parse $ARGUMENTS:
--scope <area>: Limit discovery to a single capability area (e.g.auth,image-detection). Skips areas whose entry-point paths don't match the scope. Default: full repo.--prd <path>: Override PRD auto-detection. Repeatable — pass multiple--prdflags for multi-PRD projects. Default: every*.mddirectly underdocs/prds/.--no-write: Print the audit to the conversation only; don't write todocs/blueprint/audits/.--report-only: Skip the Step 8 "What next?" prompt. Useful when running this skill from another orchestrator.
What ships with it
8 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.
- REFERENCE.md 8.6 KB
- references/agent-briefs.md 1.3 KB
- references/agentic-optimizations.md 839 B
- references/artifact-sections.md 663 B
- references/manifest-update.md 830 B
- references/tier-ranking.md 626 B
- references/workflow-harness.md 1.4 KB
- workflows/blueprint-story-audit.workflow.js 16 KB runs code
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.
- 6d ago Changed 0b5cc1c192de
- 9d ago Changed · -73 lines e7fdd50d92b6
- 20d ago Changed · +4 lines 7d3f4e7bf7d0
- 1mo ago First seen · 246 lines · 38 tokens per session scan A 979b44d31bf9
blueprint-story-audit is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 2,528 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
phpunit-integration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-integration-test-generation
Use this skill when the user asks to generate, write, or create integration tests for a Shopware 6 source class whose contract requires wired-up code — phrases like "generate integration tests for X", "write an integration test for this controller", "test this indexer", "create an integration test for the message…
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…