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-workspace-scangit 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-workspace-scan)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-workspace-scan"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-workspace-scan/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-workspace-scan"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-workspace-scan.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.00033 | $0.01034 |
| Opus 5.5 | $0.00013 | $0.00414 |
| Sonnet 5.5 | $0.00007 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
blueprint-workspace-scan 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blueprint:workspace-scan
Refresh the monorepo root blueprint's workspaces.children registry by walking
the filesystem for child docs/blueprint/manifest.json files, reading their
feature-tracker.json when present, and writing cached rollup stats back to the
root manifest.
When to Use This Skill
| Use this skill when... | Use /blueprint:status instead when... |
|---|---|
| Adding or removing a child blueprint | Just inspecting overall blueprint state |
Root workspaces.children looks stale |
You do not run a monorepo |
Migrating to format_version 3.3.0 |
You only want per-project details |
Context
- Root manifest: !
find . -path '*/docs/blueprint/*' -maxdepth 3 -name manifest.json - Candidate child manifests: !
find . -maxdepth 6 -type d \( -name node_modules -o -name .git -o -name dist -o -name build \) -prune -o -type f -path '*/docs/blueprint/manifest.json' -print - Current scan time: !
date -u +%Y-%m-%dT%H:%M:%SZ
Parameters
Parse these from $ARGUMENTS:
--dry-run: Preview discovered children and the JSON that would be written — make no changes.--max-depth N: Maximum directory depth to search (default 4). Increase for deeply nested monorepos.
Execution
Execute this workspace scan:
Step 1: Verify a root manifest exists
If docs/blueprint/manifest.json is missing, stop and report that the current
directory is not a blueprint root. Suggest /blueprint:init for new projects.
Step 2: Run the scan script
Invoke the bundled script; it walks the tree, writes the updated manifest, and emits a structured summary:
bash "${CLAUDE_SKILL_DIR}/scripts/workspace-scan.sh" \
--project-dir "$(pwd)" \
--max-depth 4 $ARGUMENTS
The script:
- Refuses to run on a manifest whose
workspaces.role == "child". - Skips
node_modules,.git,dist,build,target,.venv. - Writes
workspaces.role=root,discovery_strategy=auto-cache,last_scanned_at, and a refreshedchildren[]array withcached_stats. - Leaves existing feature-tracker data untouched.
What ships with it
1 file 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.
- 1mo ago First seen · 105 lines · 33 tokens per session scan A 873fe8be172f
blueprint-workspace-scan is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,034 once invoked, about $0.0001 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
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, and loop-lane telemetry freshness; never mutates issues, PRs, labels, or comments. Use when: 'morning brief', 'ops dashboard', 'what needs attention'…
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…
podio-ticket-updates
Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.
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…
tracker-writing
Write Jira issues, Jira comments, and GitHub pull request titles and bodies for the openEHR specification trackers and repos. Use whenever text is about to be posted to Jira or GitHub: create or edit an issue, comment, open a PR, write a review comment. Hard length caps, a fixed structure per text type, ask before…
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.