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 agentmods add commands/peterblazejewicz/claude-plugins/specgit clone --depth 1 https://github.com/peterblazejewicz/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/commands/peterblazejewicz/claude-plugins/spec)<a href="https://agentmods.dev/commands/peterblazejewicz/claude-plugins/spec"><img src="https://agentmods.dev/badge/commands/peterblazejewicz/claude-plugins/spec.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00019 | $0.00304 |
| Opus 5 | $0.00010 | $0.00152 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
spec 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 3d 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.
What it actually says
Invoke the dotnet-skills:spec-driven-development skill.
Begin by understanding what the user wants to build. Ask clarifying questions about:
- The objective and target users
- Core features and acceptance criteria
- Tech stack preferences and constraints (target framework, UI framework — Avalonia / Blazor / ASP.NET Core / .NET MAUI — data layer, test framework)
- Known boundaries (what to always do, ask first about, and never do)
Then generate a structured spec covering all six core areas: objective, dotnet CLI commands, solution/project structure, code style (including .editorconfig / analyzer-level conventions), testing strategy (xUnit v2 or v3, or MSTest), and boundaries.
Save the spec as SPEC.md in the repo root and confirm with the user before proceeding.
Source & Modifications
- Upstream:
addyosmani/agent-skills—.claude/commands/spec.mdat pinned SHA44dac80 - Status: modified (skill reference retargeted to the
dotnet-skills:prefix; clarifying questions reframed around .NET target framework / UI framework / data layer / test framework; spec output fields reframed fordotnetCLI and.editorconfig)
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.
- 3d ago First seen · 24 lines · 19 tokens per session scan A 8411c4d1f7d3
spec is a command published in the GitHub repository peterblazejewicz/claude-plugins (7 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 304 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
brownfield-map
Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.
security-review
Depth-first security audit of the current git diff — OWASP Top 10, secret leakage, insecure-by-default APIs, and language-specific foot-guns. Pass a PR number to audit a specific PR's diff.
pre-ship
Run the pre-ship quality gate checklist before publishing your agent.
rclone_copy
Copy files from source to dest, skipping identical files.
rclone_checksum
Checks the files in the destination against a SUM file.