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/data-wise/claude-plugins/spec-reviewgit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.00016 | $0.02414 |
| Opus 5 | $0.00008 | $0.01207 |
| Sonnet 5 | $0.00003 | $0.00483 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
spec-review 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 2d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec:review - Spec Review & Management
Interactive review of formal specs with validation, status updates, and archival.
Arguments
| Argument | What it does |
|---|---|
| (none) | List all specs in project |
[topic] |
Review specific spec |
list |
List all specs with status |
show [topic] |
Display spec content |
review [topic] |
Interactive review with validation |
approve [topic] |
Mark spec as approved |
archive [topic] |
Move to archive (completed) |
When Invoked
Step 1: Locate Specs
# Find specs in project
find docs/specs -name "SPEC-*.md" -type f 2>/dev/null
# If no specs directory, check root
find . -maxdepth 1 -name "SPEC-*.md" -type f 2>/dev/null
Step 2: Parse Action
| Input | Behavior |
|---|---|
/spec:review |
List all specs, then ask which to review |
/spec:review auth |
Review spec matching "auth" |
/spec:review list |
Show all specs with status |
/spec:review approve auth |
Mark auth spec as approved |
Actions
Action: list
Show all specs with their status:
┌─────────────────────────────────────────────────────────────┐
│ 📋 SPECS IN PROJECT │
├─────────────────────────────────────────────────────────────┤
│ │
│ Active Specs: │
│ 📝 SPEC-auth-system-2025-12-30.md │
│ Status: draft │ Created: 2025-12-30 │
│ Open Questions: 2 │
│ │
│ ✅ SPEC-notifications-2025-12-28.md │
│ Status: approved │ Created: 2025-12-28 │
│ Ready for implementation │
│ │
│ 🔧 SPEC-cache-layer-2025-12-25.md │
│ Status: implementing │ Created: 2025-12-25 │
│ In progress │
│ │
│ Archived: 3 specs in docs/specs/_archive/ │
│ │
├─────────────────────────────────────────────────────────────┤
│ 🔗 Actions: │
│ /spec:review [topic] ← review a spec │
│ /spec:review approve [t] ← mark as approved │
│ │
└─────────────────────────────────────────────────────────────┘
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.
- 2d ago First seen · 391 lines · 16 tokens per session scan A fcc41cabea2c
spec-review is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 2,414 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.