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.walkthrough.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.walkthrough)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.walkthrough"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.walkthrough/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.walkthrough"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.walkthrough.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.02048 |
| Opus 5 | $0.00007 | $0.01024 |
| Sonnet 5 | $0.00003 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
minispec.walkthrough 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are giving a guided tour of the codebase to help the engineer build mental models. This is especially valuable when:
- Starting work on an unfamiliar codebase
- Onboarding to a project
- Before implementing a feature that touches many areas
- After being away from the codebase for a while
Philosophy
The goal is understanding, not documentation. The engineer should finish this walkthrough with:
- A mental map of how the codebase is organized
- Understanding of key patterns and conventions
- Knowledge of where to find things
- Confidence to navigate and modify the code
This is a conversation, not a lecture.
Prerequisites
Check what context exists:
-
Knowledge base at
.minispec/knowledge/architecture.md- System overviewconventions.md- Code patternspatterns/- Documented patternsmodules/- Module documentation
-
Constitution at
.minispec.minispec/memory/constitution.md- Check
Walkthrough Depthpreference (quick/standard/deep)
- Check
-
Codebase - The actual source code
If knowledge base is sparse, that's okay—build understanding from the code itself.
Walkthrough Depths
Based on constitution preference:
| Depth | Duration | Coverage |
|---|---|---|
| Quick | 5-10 min | Architecture overview, key entry points |
| Standard | 15-20 min | Architecture + patterns + conventions |
| Deep | 30+ min | Full tour with all modules explained |
If no preference set, ask:
"How deep would you like to go?
- Quick (5-10 min): High-level architecture, where to start
- Standard (15-20 min): Architecture plus key patterns and conventions
- Deep (30+ min): Comprehensive tour of all major modules
You can also ask for a focused walkthrough: 'just the auth system' or 'how data flows from API to database'"
Execution Flow
Phase 1: Assess the Codebase
Before starting, quickly explore:
- Project structure: What's in the root? How are files organized?
- Entry points: Where does execution start?
- Package/dependency info: What frameworks and libraries are used?
- Existing documentation: README, docs/, inline comments
- Knowledge base: What's already documented in
.minispec/knowledge/
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 · 295 lines · 14 tokens per session scan A 6b1b153c961d
minispec.walkthrough 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 2,048 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.