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/mikececco/mastro/idoneogit clone --depth 1 https://github.com/mikececco/mastroWrote 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/mikececco/mastro/idoneo)<a href="https://agentmods.dev/commands/mikececco/mastro/idoneo"><img src="https://agentmods.dev/badge/commands/mikececco/mastro/idoneo.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.00026 | $0.00330 |
| Opus 5 | $0.00013 | $0.00165 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
idoneo 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 4d 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
Segui le regole in ${CLAUDE_PLUGIN_ROOT}/knowledge/regole.md — in particolare la §5:
non affermare mai l'idoneità.
Situazione descritta dall'utente: $ARGUMENTS
Procedura:
- Leggi
${CLAUDE_PLUGIN_ROOT}/knowledge/2026/esclusioni.mdeforfettario.md. - Confronta la situazione descritta con ogni causa di esclusione e ogni soglia.
- Output in tre parti:
- Cause ostative che vedo nella situazione descritta (ognuna con citazione).
- Cosa non posso valutare perché l'utente non ha dato il dato → chiediglielo esplicitamente (es. partecipazioni societarie, % verso ex datore, residenza).
- Conclusione: mai "sì, sei idoneo". Al massimo: "Non vedo cause ostative tra quelle che conosco e che mi hai descritto, ma l'idoneità va confermata col commercialista."
- Chiudi con il disclaimer.
Ricorda: una causa di esclusione che l'utente non ha menzionato può comunque escluderlo. Per questo non si dà mai il via libera.
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.
- 4d ago First seen · 23 lines · 26 tokens per session scan A c1f257c28c1d
idoneo is a command published in the GitHub repository mikececco/mastro (3 stars, last pushed 24d ago), licensed MIT. It adds 26 tokens to every session and 330 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
review-claims
Analyze patent claims for 35 USC 112(b) compliance - antecedent basis, definiteness, and claim structure.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-epo-formalities
Check patent application formalities for EPO compliance (Rules 42-49 EPC, EPO Guidelines Part A).
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.