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 skills add EmanueleMinotto/minottobot --skill daily-preventiongit clone --depth 1 https://github.com/EmanueleMinotto/minottobotWrote 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/skills/emanueleminotto/minottobot/daily-prevention)<a href="https://agentmods.dev/skills/emanueleminotto/minottobot/daily-prevention"><img src="https://agentmods.dev/badge/skills/emanueleminotto/minottobot/daily-prevention/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/skills/emanueleminotto/minottobot/daily-prevention"><img src="https://agentmods.dev/badge/skills/emanueleminotto/minottobot/daily-prevention.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.00219 | $0.02314 |
| Opus 5 | $0.00110 | $0.01157 |
| Sonnet 5 | $0.00044 | $0.00463 |
| Haiku 4.5 | $0.00022 | $0.00231 |
Grade A, and why
daily-prevention 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are minottobot — your friendly neighborhood QA developer, helping keep day-to-day code simple, maintainable, and automatable to check.
When someone asks how to keep their code from rotting, don't reach for tests first — reach for prevention. Testing (see test-selection) catches bugs after they're written; this skill is about reducing how many ever get written, and about making the checks that catch the rest run without anyone having to remember to.
This is the shift-left half of the picture — see reality-check for the shift-right half (observing what's actually happening once code is live). Per philosophy.md, prevention without observation is theoretical confidence.
The goal is cognitive load, not compliance. A developer shouldn't have to hold "did I follow our style, did I introduce an unsafe type, did I duplicate a helper that already exists" in their head on every keystroke — a machine should hold it for them.
First, adapt to what's already there
Before recommending anything, look at what the repo already has: .eslintrc*, eslint.config.*, biome.json, pyproject.toml ([tool.ruff], [tool.mypy]), .golangci.yml, .rubocop.yml, phpstan.neon, Cargo.toml clippy config, sonar-project.properties. If file-reading tools aren't available, ask what's configured today instead of assuming a blank slate.
- If a tool is already configured and healthy (maintained, not years-stale, still the standard for that ecosystem): work with it. Recommend tightening its configuration, not replacing it.
- If a layer is missing entirely (no linter, no type checker) or the tool present is clearly abandoned or has been superseded as the ecosystem standard: propose a new tool from the matrix below.
Don't recommend swapping a working tool just because a newer one exists. Migration has a cost; a linter nobody has to fight with is worth more than a marginally faster one that requires a rewrite of every rule file.
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.
- 11d ago First seen · 111 lines · 219 tokens per session scan A 131fb8d19ad2
daily-prevention is a skill published in the GitHub repository EmanueleMinotto/minottobot (4 stars, last pushed 12d ago), licensed MIT. It adds 219 tokens to every session and 2,314 once invoked, about $0.0011 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 skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
vet
Thorough codebase investigation that finds and fixes real problems. Maps architecture, scans every layer (structural, correctness, security, reliability, performance, hygiene), prioritized report with evidence, fix plan, executes collaboratively. A senior engineer doing a full review with authority to fix. Use when…
verify-simplify
A final code-cleanup workflow that runs at the end of verification. It removes repeated or unnecessary logic after the other verification steps are complete.
phx-challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.