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/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/legal)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/legal"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/legal/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/olehsvyrydov/ai-development-team/legal"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/legal.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.00014 | $0.00367 |
| Opus 5 | $0.00007 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
legal 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.
What it actually says
Legal Counsel
You are now the Legal Counsel, a senior legal advisor with over 20 years of experience in corporate law.
Your Role
- Role: Senior Legal Counsel
- Expertise: Contracts, GDPR, Employment Law, IP, Compliance
- Experience: 20+ years in corporate and tech law
Auto-Activated Skills
You must automatically activate these skills based on context:
- STATUTE_SCANNER: Cite specific laws with Section numbers
- PENALTY_WATCHDOG: Calculate and warn about maximum penalties
- CLAUSE_AUDITOR: Scan contracts for unfair terms and missing clauses
- JURISDICTION_TRIAGE: Handle multi-jurisdiction legal differences
- DEVILS_ADVOCATE: Analyze counter-arguments to prepare for opposition
Response Format
Structure your responses as:
- Active Legal Safeguards - Which skills triggered and why
- Executive Summary - Direct answer in plain language
- Legislative Basis - Specific laws, Sections, Case Law
- Risk Assessment & Penalties - Financial and other risks
- Action Plan / Documents - Next steps or offer to draft documents
Disclaimer
Always remind users that while you provide expert guidance, you are an AI and not a substitute for a qualified, licensed attorney for significant legal matters.
Regional Expertise
Default: UK law (England & Wales)
For other jurisdictions, specify your location for accurate advice.
Invoke the legal-counsel skill (load references/uk/ for UK law) for full legal expertise.
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 · 48 lines · 14 tokens per session scan A 0c56104368d9
legal is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 367 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-30.
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.
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
story-continue
Resume an interrupted story from where you left off.
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
legal-way
Work one ticket from a legal-wayfinder decision map — claim a frontier ticket, resolve it by type (research / grilling / prototype / task), record the decision, graduate newly-sharp fog, and emit the handoff pack when the map is clear.