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.validate-docs.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.validate-docs)<a href="https://agentmods.dev/commands/ivo-toby/mcp-picnic/minispec.validate-docs"><img src="https://agentmods.dev/badge/commands/ivo-toby/mcp-picnic/minispec.validate-docs.svg" alt="Measured on agentmods" 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.00010 | $0.01830 |
| Opus 5 | $0.00005 | $0.00915 |
| Sonnet 5 | $0.00002 | $0.00366 |
| Haiku 4.5 | $0.00001 | $0.00183 |
Grade A, and why
minispec.validate-docs 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 8d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You are performing a documentation health check to ensure the knowledge base stays accurate as the codebase evolves. Stale documentation is worse than no documentation—it misleads.
Philosophy
Documentation should:
- Reflect the current state of the code
- Be trustworthy for both humans and AI
- Stay current without manual effort
This command catches drift between code and docs, then helps fix it.
What to Validate
1. Decision Records (.minispec/knowledge/decisions/)
For each decision file:
Frontmatter validity:
- Required fields present (type, id, date, status, impacts)
- Status is valid (proposed/accepted/deprecated/superseded)
- If superseded,
superseded_bypoints to existing decision
Content accuracy:
- Code references still exist
- Referenced file paths are valid
- Impacts list matches actual file locations
Relevance:
- Decision hasn't been reversed without documentation
- Status reflects reality (is it still active?)
2. Pattern Documentation (.minispec/knowledge/patterns/)
For each pattern file:
Frontmatter validity:
- Required fields present (type, id, name, category, status)
- Status reflects current usage
Content accuracy:
- Code examples match actual patterns in codebase
- "Examples in This Codebase" locations exist
- Referenced files use the pattern as described
Relevance:
- Pattern is actually used (not deprecated in practice)
- No newer pattern has replaced it
3. Module Documentation (.minispec/knowledge/modules/)
For each module file:
Frontmatter validity:
- Required fields present (type, id, name, path, status)
- Path points to existing directory
Content accuracy:
- Public API matches actual exports
- Listed files exist
- Dependencies are accurate
Relevance:
- Module still exists
- Architecture description matches reality
4. Architecture Overview (.minispec/knowledge/architecture.md)
Structural accuracy:
- Described components exist
- Relationships are accurate
- Tech stack is current
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.
- 8d ago First seen · 270 lines · 10 tokens per session scan A 8ab52e7f698d
minispec.validate-docs is a command published in the GitHub repository ivo-toby/mcp-picnic (98 stars, last pushed 24d ago), licensed MIT. It adds 10 tokens to every session and 1,830 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.