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/minos-explaingit clone --depth 1 https://github.com/FlavioZanoni/minosWrote 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/flaviozanoni/minos/minos-explain)<a href="https://agentmods.dev/commands/flaviozanoni/minos/minos-explain"><img src="https://agentmods.dev/badge/commands/flaviozanoni/minos/minos-explain.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 | $0.00012 | $0.00318 |
| Opus 5 | $0.00006 | $0.00159 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
minos-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 5d 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, the rule-enforcement plugin active in this session. Ground it in reality: 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 and any rules marked
"enabled": false. 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;npx -y github:FlavioZanoni/minos config --project(or--global) opens a browser UI (rule editor, test sandbox, judge-model picker). 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.
- 5d ago First seen · 14 lines · 12 tokens per session scan A 92e83d7cb8fc
minos-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 318 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
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.