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-feature-tracker-statusgit 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-feature-tracker-status)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/blueprint-feature-tracker-status"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-feature-tracker-status/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-feature-tracker-status"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/blueprint-feature-tracker-status.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 7 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.00036 | $0.02140 |
| Opus 5.5 | $0.00014 | $0.00856 |
| Sonnet 5.5 | $0.00007 | $0.00428 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
blueprint-feature-tracker-status 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Display feature tracker statistics, phase progress, and completion summary.
When to Use This Skill
| Use this skill when... | Use blueprint-feature-tracker-sync instead when... |
|---|---|
| You want a read-only view of completion stats and phase progress | You need to reconcile TODO.md with the tracker (writes) |
| You want to see PRD coverage and ready-to-start work | You want to drain WO entries via --drain-wave |
| You're checking blocked features without modifying state | You want to recalculate completion percentages |
| You want a quick "where are we?" snapshot | Use feature-tracking instead for low-level FR-code edits |
Steps
-
Check if feature tracking is enabled:
- Look for
docs/blueprint/feature-tracker.json - If not found, report:
Feature tracking not enabled in this project. Run `/blueprint:init` and enable feature tracking to get started.
- Look for
-
Load tracker data:
- Read
feature-tracker.json - Extract project name, source document, last_updated
- Get statistics section
- Get phase information
- Get PRD status
- Read
-
Calculate derived metrics (if not in statistics):
- Count features by status at all nesting levels
- Calculate completion percentage
- Count features per phase
- Count PRDs by status
3a. Confirm the statistics cache is trustworthy (read-only):
Everything this skill displays is quoted from statistics, which is a
cache of the features collection — so verify it before quoting it:
bash "${CLAUDE_SKILL_DIR}/../../scripts/blueprint-tracker-check.sh" --project-dir "$(pwd)"
On STATUS=ERROR with TYPE=statistics_divergence rows, display the
recomputed EXPECTED= figures (not the cached ones) and add a line to the
report: Statistics cache is stale — run /blueprint:feature-tracker-sync.
Surface any other ISSUES: rows verbatim under a "Tracker Integrity"
heading. This skill never writes, so it reports and defers the fix to
/blueprint:feature-tracker-sync (its Step 7a).
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 · 254 lines · 36 tokens per session scan A 6cf9bd2daeaf
blueprint-feature-tracker-status is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,140 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.