Borrowing it
Nothing to install: this file belongs to ivo-toby/mcp-picnic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ivo-toby/mcp-picnic/main/.claude/commands/minispec.analyze.mdgit clone --depth 1 https://github.com/ivo-toby/mcp-picnicWrote 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/ivo-toby/mcp-picnic/minispec.analyze)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.analyze"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.analyze/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/commands/ivo-toby/mcp-picnic/minispec.analyze"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.analyze.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.01663 |
| Opus 5 | $0.00006 | $0.00831 |
| Sonnet 5 | $0.00003 | $0.00333 |
| Haiku 4.5 | $0.00001 | $0.00166 |
Grade A, and why
minispec.analyze 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 10d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are performing a pre-implementation validation to catch issues before they become expensive to fix. This is a conversation about readiness, not just a report dump.
Philosophy
The goal isn't to generate a lengthy report—it's to answer one question: "Are we ready to start implementing?"
If yes, confirm and move on. If no, explain what needs attention and help fix it.
Prerequisites
Verify these artifacts exist:
- Constitution at
.minispec.minispec/memory/constitution.md - Design at
.minispec/specs/[feature-name]/design.md - Tasks at
.minispec/specs/[feature-name]/tasks.md - Decisions in
.minispec/knowledge/decisions/
If $ARGUMENTS specifies a feature, use that. Otherwise, detect the current feature or ask.
If any required artifact is missing:
"I can't run a full analysis yet. Missing:
- Constitution ✓
- Design - Run
/minispec.designfirst- Tasks - Run
/minispec.tasksfirstWant me to help with the missing piece?"
Analysis Areas
1. Design ↔ Tasks Alignment
Check that every design element has corresponding tasks:
Components:
- Each component in design.md should have implementation tasks
- Flag components with no associated tasks
Decisions:
- Each decision in
.minispec/knowledge/decisions/should be reflected in tasks - Flag decisions that imply work but have no tasks
Data Model:
- Each entity should have model/migration tasks
- Flag entities missing from task list
API/Interface:
- Each endpoint/function should have implementation tasks
- Flag APIs without coverage
2. Task Completeness
Check that tasks are well-formed:
Required elements:
- Estimate (lines)
- Files affected
- Description
- Acceptance criteria
Dependency validity:
- No circular dependencies
- Dependencies reference existing tasks
- Order makes sense (can't integrate before building)
Size appropriateness:
- Compare estimates against constitution chunk size preference
- Flag tasks significantly over/under target size
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.
- 10d ago First seen · 271 lines · 13 tokens per session scan A 30c67a1c5881
minispec.analyze is a command published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 26d ago), licensed MIT. It adds 13 tokens to every session and 1,663 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-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.