Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/flaviozanoni/minos/explaingit clone --depth 1 https://github.com/FlavioZanoni/minosWhat 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 | $0.00012 | $0.00316 |
| Opus 5 | $0.00006 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
explain 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 2d 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.
What it actually says
Give the user a short, beginner-friendly explanation of minos. To ground it in reality, first read ${CLAUDE_PLUGIN_ROOT}/README.md, then read the user's config files if they exist: ~/.config/minos/rules.jsonc (global) and .minos/rules.jsonc (current project).
Cover, in this order:
- What it is (2-3 sentences): minos hooks into every shell command and file edit/write this agent makes and checks them against configured rules - blocking or warning before bad actions land, no matter how long the session gets.
- What's active here: list the currently effective rules for this project in a compact table (rule id, what it catches, warn/block, global or project). Note any global rules the project disables. If no config exists yet, say so and show one minimal example rule.
- How to configure:
/minos:configure <plain-language request>has the agent write and verify a rule for you;/global-configand/project-configopen a browser UI (rule editor, test sandbox to try commands/edits against the rules, and the judge-model setting for AI-judgment rules). Power users can edit the JSONC files directly - project rules override global ones by id, and"disable": [...]turns global rules off per-project.
Keep it under ~30 lines, no raw JSON dumps unless the user asks.
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.
- 2d ago First seen · 14 lines · 12 tokens per session scan A 34411a81c4dd
explain is a command published in the GitHub repository FlavioZanoni/minos (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 316 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-31.
Other commands, from other repositories
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.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.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.