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/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/legal-check)<a href="https://agentmods.dev/commands/pedrol-cmd/brain-drin/legal-check"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/legal-check/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/pedrol-cmd/brain-drin/legal-check"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/legal-check.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.00011 | $0.00088 |
| Opus 5.5 | $0.00004 | $0.00035 |
| Sonnet 5.5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
legal-check 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 1mo 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
/legal-check
Sanity check for the legal safety of your operations.
Usage
- Provide a contract clause, technical choice (LLM usage), or policy.
- Agent flags risks and compliance gaps (GDPR/LGPD/Licensing).
Specialist Agent
@legal-compliance
skill: drin-legal-risk-assessment
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.
- 1mo ago First seen · 17 lines · 11 tokens per session scan A 79ddc585aa37
legal-check is a command published in the GitHub repository pedrol-cmd/brain-drin (12 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 88 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
auditoria-legal
Grupo: Trabajo con el framework En una frase: Auditoría de cumplimiento legal del producto — territorio, evidencia y lo que el código no cubre. Cuándo: Antes de publicar una app o web: registro, cookies, analítica, emails, suscripciones, contenido de usuarios. Quién: Cualquier operador del repo.