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.
git 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/commands/capazme/mcp-legal-it/release)<a href="https://agentmods.dev/commands/capazme/mcp-legal-it/release"><img src="https://agentmods.dev/badge/commands/capazme/mcp-legal-it/release/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/commands/capazme/mcp-legal-it/release"><img src="https://agentmods.dev/badge/commands/capazme/mcp-legal-it/release.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.00056 | $0.01619 |
| Opus 5 | $0.00028 | $0.00809 |
| Sonnet 5 | $0.00011 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
release 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 10d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comando /release
Alternativa automatizzata:
python3 release.py --from-developesegue tutti questi step con bump automatico di tutti i 6 manifest, conteggio tool, verifica pre-tag e rollback in caso di errore. Usalo se possibile.
Segui questi step ESATTAMENTE nell'ordine indicato. Non saltare nessun passaggio.
Step 1 — Determina la versione
L'utente fornisce la versione target (es. 2.4.0). Se non la fornisce, leggi la versione attuale da pyproject.toml e proponi il bump appropriato:
- PATCH (Z+1): bug fix, aggiornamento dati
- MINOR (Y+1): nuovi tool, nuove feature
- MAJOR (X+1): breaking change nelle API dei tool
Step 2 — Conta i tool attuali
grep -c "@mcp.tool" plugin/server/src/tools/*.py | awk -F: '{sum+=$2} END {print sum}'
Salva il numero — serve per aggiornare le description.
Step 3 — Verifica test
.venv/bin/pytest tests/unit/ -q --tb=short
Se ci sono fallimenti, STOP. Non procedere con la release.
Step 4 — Crea release branch
git checkout develop
git pull origin develop
git checkout -b release/X.Y.Z
Step 5 — Bumpa la versione in TUTTI i 6 file
Sostituisci la versione precedente con la nuova in OGNUNO di questi file:
pyproject.toml→version = "X.Y.Z"plugin/server/pyproject.toml→version = "X.Y.Z"dxt/manifest.json→"version": "X.Y.Z"plugin/server/manifest.json→"version": "X.Y.Z"plugin/.claude-plugin/plugin.json→"version": "X.Y.Z".claude-plugin/marketplace.json→"version": "X.Y.Z"(dentroplugins[0])
Step 6 — Aggiorna le description con il conteggio tool corretto
Aggiorna il numero di tool nelle description di questi 4 file (usa il conteggio dello Step 2):
dxt/manifest.json→ campo"description"plugin/server/manifest.json→ campo"description"plugin/.claude-plugin/plugin.json→ campo"description".claude-plugin/marketplace.json→ campo"description"dentroplugins[0]
Step 7 — Aggiorna i changelog
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.
- 10d ago First seen · 161 lines · 56 tokens per session scan A aebd9144cdb3
release is a command published in the GitHub repository capazme/mcp-legal-it (15 stars, last pushed 10d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,619 once invoked, about $0.0003 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 commands, from other repositories
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
gsd:complete-milestone
Archive completed milestone and prepare for next version.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.
rebase_prompt
You are a git rebase assistant. Your job is to rebase the current branch onto origin/ and intelligently resolve any merge conflicts that arise. The repository has already been fetched and the base branch is ; you may assume origin/ is up-to-date.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
release
../../templates/commands/release.md.