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.status.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.status)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.status"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.status/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.status"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.status.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.00012 | $0.01628 |
| Opus 5 | $0.00006 | $0.00814 |
| Sonnet 5 | $0.00002 | $0.00326 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
minispec.status 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are providing a quick status update on where things stand. This is the "dashboard view" of the MiniSpec workflow.
Philosophy
Engineers should be able to:
- Quickly understand where they are in the process
- See what's done and what's remaining
- Know the next action to take
- Get context after stepping away
Keep it concise but complete.
Execution Flow
Phase 1: Gather State
Read current state from:
-
Constitution (
.minispec.minispec/memory/constitution.md)- Project name
- MiniSpec preferences
-
Active features (
.minispec/specs/*/)- Which features are in progress
- Status of each (designed/planned/implementing/complete)
-
Current feature details (if one is active)
- Design status
- Task progress
- Recent activity
-
Knowledge base (
.minispec/knowledge/)- Number of decisions
- Last updates
Phase 2: Determine Context
Figure out what to show based on state:
No features yet:
Project is set up but no features started
Feature in design:
Currently designing [feature], not yet planned
Feature planned, not started:
[Feature] is planned with [N] tasks, ready to implement
Feature in progress:
Implementing [feature], [N]/[M] tasks complete
Feature complete:
[Feature] complete, no active work
Phase 3: Display Status
Compact Status (Default)
📍 MiniSpec Status
Project: [Project Name]
Active Feature: [Feature Name] (or "None")
Phase: [Design | Planning | Implementation | Idle]
Progress: [N]/[M] tasks ([%]%)
████████░░░░
Next: [Description of next action]
Run: /minispec.[command]
Last activity: [Time ago] - [What was done]
Detailed Status (if requested or complex state)
📍 MiniSpec Status: [Project Name]
═══════════════════════════════════════════
CURRENT FEATURE: [Feature Name]
Status: [Designing | Planned | Implementing | Complete]
┌─ Design ─────────────────────────────────
│ ✅ Complete
│ Decisions: 3 documented
│ Components: 4 defined
└──────────────────────────────────────────
┌─ Tasks ──────────────────────────────────
│ Total: 8 tasks (~320 lines)
│ Complete: 3 ✅
│ In Progress: 1 🔄
│ Remaining: 4 ⏳
│
│ Progress: ████████░░░░░░░░ 37%
│
│ Current: Task 4 - Auth middleware
│ Next: Task 5 - Protected routes
└──────────────────────────────────────────
┌─ Recent Activity ────────────────────────
│ 2h ago: Completed Task 3 (Login endpoint)
│ 3h ago: Completed Task 2 (User model)
│ Yesterday: Design approved
└──────────────────────────────────────────
KNOWLEDGE BASE
├─ Decisions: 5 (2 new this feature)
├─ Patterns: 3
├─ Modules: 2
└─ Last validated: [Date]
NEXT ACTION
→ Continue implementation: /minispec.next
Task 4: Auth middleware (~50 lines)
═══════════════════════════════════════════
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 · 261 lines · 12 tokens per session scan A c717dd8a7a53
minispec.status is a command published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 1,628 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.