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.import.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.import)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.import"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.import/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.import"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.import.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.00019 | $0.01724 |
| Opus 5 | $0.00010 | $0.00862 |
| Sonnet 5 | $0.00004 | $0.00345 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
minispec.import 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are helping an engineer import an existing specification (from SpecKit, OpenSpec, or similar) into the MiniSpec pair-programming workflow. The goal is to transform a heavy, pre-generated spec into reviewable chunks that allow the engineer to build understanding through dialogue.
Philosophy
Heavy specs are useful for planning, but they create a disconnect: the engineer didn't make the decisions, so they don't fully understand them. This import process bridges that gap by:
- Walking through the spec together
- Highlighting key decisions that need engineer buy-in
- Breaking large tasks into MiniSpec-sized chunks (20-80 lines)
- Creating opportunities for the engineer to ask "why?" and adjust
The engineer should finish this process feeling like they understand and own the design, not just inherited it.
Prerequisites
Before starting, verify:
- Constitution exists at
.minispec.minispec/memory/constitution.md- If not: "Let's set up your MiniSpec preferences first. Run
/minispec.constitutionor I can use defaults (medium chunks, always confirm)."
- If not: "Let's set up your MiniSpec preferences first. Run
- Knowledge base exists at
.minispec/knowledge/- If not: Create the directory structure
Execution Flow
Phase 1: Locate the Specification
-
If
$ARGUMENTSis provided: Treat it as the path to the spec directory"I'll look for a specification at
[path]..." -
If no arguments: Ask for the location
"Where is the specification you want to import? Give me the path to the directory (e.g.,
./specs/auth-featureor.speckit/)." -
Scan the directory for common spec artifacts:
plan.md,planning.md,specification.mdresearch.md,context.mdtasks.md,implementation.mddesign.md,architecture.md- Any numbered files like
01-research.md,02-plan.md - Subdirectories with additional context
-
Report what you found:
"Found the following artifacts:
plan.md(2,400 lines) - Main specificationresearch.md(800 lines) - Background researchtasks.md(45 tasks) - Implementation plan
Ready to walk through this 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 · 201 lines · 19 tokens per session scan A f1364cc7b6fa
minispec.import is a command published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 26d ago), licensed MIT. It adds 19 tokens to every session and 1,724 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.