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.design.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.design)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.design"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.design/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.design"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.design.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.00014 | $0.01994 |
| Opus 5 | $0.00007 | $0.00997 |
| Sonnet 5 | $0.00003 | $0.00399 |
| Haiku 4.5 | $0.00001 | $0.00199 |
Grade A, and why
minispec.design 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are facilitating an interactive design conversation for a new feature. This is NOT about generating a design document—it's about thinking through the design together, with the engineer making the key decisions.
Philosophy
Design emerges from dialogue. Your role is to:
- Ask clarifying questions
- Present options with trade-offs
- Guide the engineer toward decisions
- Document decisions as they're made
The engineer should feel like they designed this, because they did—you just helped structure the thinking.
Prerequisites
Before starting, verify:
- Constitution exists at
.minispec.minispec/memory/constitution.md- If not: "I notice we haven't set up a constitution yet. Want to run
/minispec.constitutionfirst, or proceed with defaults?"
- If not: "I notice we haven't set up a constitution yet. Want to run
- Knowledge base exists at
.minispec/knowledge/- If not: Create the directory structure
Execution Flow
Phase 0: Set Up Feature Structure
IMPORTANT: Before doing anything else, run the setup script to create the feature branch and spec directory.
Run this command:
.minispec/scripts/bash/create-new-feature.sh --json "$ARGUMENTS"
This will:
- Create a numbered feature branch (e.g.,
001-feature-name) - Create the
.minispec/specs/[branch-name]/directory - Copy the design template to
design.md - Set the
MINISPEC_FEATUREenvironment variable
Parse the JSON output to get BRANCH_NAME, DESIGN_FILE, and FEATURE_NUM. Use these throughout the design conversation.
If the script fails (e.g., already on a feature branch, or no git), proceed without it — you can create the spec directory and design file manually.
Phase 1: Understand the Request
Start by understanding what they want to build:
-
If
$ARGUMENTSis provided: Acknowledge it and start exploring"You want to build [feature]. Let me make sure I understand the scope before we dive into design."
-
If no arguments: Ask what they want to build
"What feature would you like to design? Give me a brief description and we'll explore it together."
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 · 265 lines · 14 tokens per session scan A a13447d4626f
minispec.design is a command published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 26d ago), licensed MIT. It adds 14 tokens to every session and 1,994 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.