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/benjonx/legal/repondregit clone --depth 1 https://github.com/BenjoNX/LegalWrote 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/benjonx/legal/repondre)<a href="https://agentmods.dev/commands/benjonx/legal/repondre"><img src="https://agentmods.dev/badge/commands/benjonx/legal/repondre.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.1 | $0.00012 | $0.00666 |
| Opus 5 | $0.00006 | $0.00333 |
| Sonnet 5 | $0.00002 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
repondre 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repondre -- Réponse type juridique
Génère une réponse pour des demandes juridiques courantes en utilisant les modèles configurés. Adapté au droit français (RGPD, Code civil, Code du travail).
Invocation
/repondre [type-demande]
Types de demandes :
droit-acces-- Demande d'exercice de droits RGPD (accès, suppression, rectification, portabilité)conservation-- Avis de conservation de documents (litigation hold)nda-- Demande de NDA par une équipe métierfournisseur-- Question juridique d'un fournisseurcnil-- Réponse à un contrôle ou questionnaire CNILmise-en-demeure-- Réponse à une mise en demeuresous-traitant-- Questions sur le contrat de sous-traitance RGPD
Workflow
Étape 1 : Identifier le type de demande
Si ambigu, afficher les catégories disponibles et demander clarification.
Étape 2 : Vérifier les déclencheurs d'escalade
Avant de générer la réponse, évaluer si la situation nécessite un traitement individualisé :
Déclencheurs universels :
- Contentieux potentiel ou enquête réglementaire
- Demande émanant d'une autorité (CNIL, DGCCRF, tribunal)
- Réponse créant un engagement juridique contraignant
- Implication d'un dirigeant
- Médiatisation
- Situation inédite
Si un déclencheur est détecté : alerter l'utilisateur, recommander l'escalade, marquer tout projet de réponse « POUR REVUE JURIDIQUE UNIQUEMENT ».
Étape 3 : Recueillir les détails
Adapter les questions au type de demande. Pour une demande RGPD par exemple :
- Nom et coordonnées du demandeur
- Type de droit exercé (accès, suppression, rectification, portabilité, opposition)
- Données concernées
- Délai de réponse (30 jours RGPD, prorogeable de 60 jours)
Étape 4 : Générer la réponse
Utiliser rechercher_legifrance() pour vérifier les textes applicables si nécessaire. Respecter :
- Le ton approprié (professionnel, clair)
- Les éléments juridiques requis (références légales, délais)
- Les prochaines étapes pour le destinataire
- Les mentions obligatoires (voies de recours CNIL, etc.)
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.
- 5d ago First seen · 83 lines · 12 tokens per session scan A dd7b89673237
repondre is a command published in the GitHub repository BenjoNX/Legal (0 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 666 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-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
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.