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-developmentgit 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-development)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-development"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-development/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-development"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Agent Snooping · line 30 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 31 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 166 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00029 | $0.01801 |
| Opus 5.5 | $0.00012 | $0.00720 |
| Sonnet 5.5 | $0.00006 | $0.00360 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade B, and why
blueprint-development scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Rules directory: !`find . -path '*/.claude/rules' -maxdepth 2 -type d` How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:development
Guide and reference for the Blueprint Development methodology that generates project-specific behavioral rules and workflow commands from PRDs (Product Requirements Documents).
When to Use This Skill
| Use this skill when... | Use alternative when... |
|---|---|
| Starting Blueprint Development in a project | Project is already using Blueprint (use /blueprint:status) |
| Need to generate rules from PRDs | Starting a brand new project with no PRD yet |
| Want project-specific behavioral guidelines | Using generic development practices |
| Creating workflow automation for a project | Working on isolated tasks without project context |
For detailed rule templates, command templates, and generation guidelines, see REFERENCE.md.
Context
- Blueprint initialized: !
find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' -type f - PRDs present: !
find . -path '*/docs/prds/*' -name "*.md" -type f - Rules directory: !
find . -path '*/.claude/rules' -maxdepth 2 -type d - Existing rules: !
find . -path '*/.claude/rules/*' -maxdepth 3 -name "*.md" - Project type: !
find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \) -type f -print -quit
Execution
Execute the complete Blueprint Development setup and rule generation workflow:
Step 1: Verify project readiness
Check the values in Context:
- If Blueprint initialized = "NO" → Error: "Blueprint not initialized. Run
/blueprint:initfirst" - If PRDs present = "0" → Error: "No PRDs found. Create at least one PRD in
docs/prds/before generating rules" - If Rules directory = "NO" → Create:
mkdir -p .claude/rules
Step 2: Analyze PRDs and extract patterns
Read all PRD files in docs/prds/ and extract:
- Architecture Patterns: Project structure, dependency injection, error handling, module boundaries, layering, code organization
- Testing Strategies: TDD workflow, test types (unit, integration, e2e), mocking patterns, coverage requirements
- Implementation Guides: Patterns for implementing feature types (APIs, UI, database, external services)
- Quality Standards: Code review checklist, performance baselines, security requirements, style standards
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.
- 6d ago Changed 6a8458b1f5d5
- 9d ago Changed · -1 lines ed2932881724
- 1mo ago First seen · 179 lines · 29 tokens per session scan B 7f5bbac894fa
blueprint-development is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,801 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
extract-ssot
Deduplicate repeated markdown (rule files, skill bodies, ADRs, docs) into one named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept recurs across files: 'DRY this prose', 'extract a shared rule', 'single source of truth for X', a value-bump diff…
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
use-class-for-state
For complex state: encapsulate multiple interacting variables, stateful algorithms, backtracking search state.
display-grid-state
For 2D debugging: visualize grid/board state, show puzzle progress, make algorithm behavior visible.
renovate-triage
Use when triaging open Renovate PRs across your own repos into merge / close / defer. Activates on "renovate triage", "review dep PRs", "monthly deps", or on the 1st of a month if deps are grouped monthly.