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 capazme/mcp-legal-it --skill analisi-fornitorigit clone --depth 1 https://github.com/capazme/mcp-legal-itWrote 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/capazme/mcp-legal-it/analisi-fornitori)<a href="https://agentmods.dev/skills/capazme/mcp-legal-it/analisi-fornitori"><img src="https://agentmods.dev/badge/skills/capazme/mcp-legal-it/analisi-fornitori/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/capazme/mcp-legal-it/analisi-fornitori"><img src="https://agentmods.dev/badge/skills/capazme/mcp-legal-it/analisi-fornitori.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00209 | $0.01866 |
| Opus 5 | $0.00105 | $0.00933 |
| Sonnet 5 | $0.00042 | $0.00373 |
| Haiku 4.5 | $0.00021 | $0.00187 |
Grade A, and why
analisi-fornitori 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 12d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analisi fornitori — screening privacy del mastrino
Qualifica ogni fornitore del mastrino rispetto al ruolo privacy nel rapporto con il cliente dello studio (il titolare del trattamento). È uno screening di primo livello: la qualifica dipende dalla prestazione CONCRETA resa al cliente, che il mastrino non rivela — l'esito va validato con cliente e contratti, e la Confidenza deve rifletterlo.
Regole d'oro (valgono in ogni fase)
- Mai inventare: attività, P.IVA e servizi si affermano solo con una fonte
(URL) o con conferma VIES. Fornitore non identificabile → categoria più
probabile + Confidenza
basso+ alternative innote. - Gli importi sono irrilevanti: ignorarli sempre.
- Confidenza al ribasso: nel dubbio, abbassa.
altoSOLO con identificazione univoca confermata (P.IVA presente o agganciata via VIES). Senza P.IVA nel mastrino,altoè l'eccezione. - Contratto canonico: ogni fornitore analizzato è un oggetto JSON con i campi
di
references/metodologia.md§Contratto. I tool lo validano — rispettalo.
Fase 0 — Setup
Chiedi (se non già noti): denominazione del cliente titolare e file del
mastrino. Crea analisi_fornitori_checkpoint.json accanto al mastrino (fallback:
directory corrente). Se esiste già un checkpoint per quel mastrino, proponi di
riprendere dal primo fornitore non analizzato invece di ripartire.
Struttura del checkpoint:
{
"versione": 1,
"cliente": "...",
"file_mastrino": "...",
"creato": "ISO-8601",
"fase": "estrazione | dedup | ricerca | completata",
"fornitori_estratti": [],
"fornitori_unici": [],
"analisi": []
}
Aggiorna il checkpoint dopo OGNI mutazione (fine estrazione, fine dedup, fine di ogni blocco di ricerca).
Fase 1 — Estrazione
Leggi il mastrino nel formato in cui arriva (guida per formato in
references/metodologia.md §Estrazione). Estrai per ogni riga: denominazione
e P.IVA/CF se presente. Se il file è illeggibile (scansione pessima, corrotto):
fermati e chiedi una copia migliore. Salva in fornitori_estratti.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 124 lines · 209 tokens per session scan A 00c44c1d475d
analisi-fornitori is a skill published in the GitHub repository capazme/mcp-legal-it (15 stars, last pushed 2d ago), licensed Apache-2.0. It adds 209 tokens to every session and 1,866 once invoked, about $0.0010 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 skills, from other repositories
grc-compliance
Build ServiceNow GRC — sncompliancepolicy lifecycle, sncompliancecontrol tests, snriskrisk assessment with inherent/residual scoring, audit engagements, and findings remediation.
vendor-management
Manage ServiceNow vendors and contracts — corecompany vendor records, astcontract with renewal alerts, astcontractsla performance tracking, vendorriskassessment scoring, and vendor scorecards.
lawyer-expert
Expert-level legal systems, contracts, compliance, and legal technology. Use when the user mentions legal, contracts, compliance, law, or legal tech, or when the task involves Legal Systems, Legal Technology, Compliance Frameworks, or Contract Management.
compliance-audit-workflow
Run a compliance audit Mistral Workflow, query mid-run findings via workflowinteract(action="query"), and signal approval or escalation decisions at checkpoints via workflowinteract(action="signal"). Use when the user wants to run a compliance audit (GDPR, SOC2, PCI-DSS, etc.) against a deployed Mistral Workflow.
contract-analyzer
OCR a contract PDF with mistralocr, then extract structured clauses and risk scores with mistralchat + jsonschema. Use when the user provides a contract document to analyze for risks, obligations, and key terms.
contract-review-workflow
Trigger a deployed Mistral Workflow for contract review, poll execution status, detect human-in-the-loop checkpoints via workflowinteract(query), collect approval or changes, and resume the workflow via workflowinteract(signal). Use when the user wants to run a contract through a Mistral Workflow with oversight…