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 event4u-app/agent-config --skill legal-practice-profilegit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/legal-practice-profile)<a href="https://agentmods.dev/skills/event4u-app/agent-config/legal-practice-profile"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/legal-practice-profile/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/event4u-app/agent-config/legal-practice-profile"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/legal-practice-profile.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.00044 | $0.03053 |
| Opus 5 | $0.00022 | $0.01527 |
| Sonnet 5 | $0.00009 | $0.00611 |
| Haiku 4.5 | $0.00004 | $0.00305 |
Grade A, and why
legal-practice-profile 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 8d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
legal-practice-profile
The keystone of the legal pack. Legal skills (contract-review, nda-triage, dpa-review, legal-intake-triage) ship procedure + output template only — no default legal positions. This skill captures the positions, in plain prose, so one generic skill set behaves team-specifically. Obeys legal-safety-floor.
When to use
- First run of the legal pack — before any review skill is invoked (they halt on
[configure]placeholders until the profile exists). - A position changed (new standard NDA term, a different escalation owner, a jurisdiction added within EU/DE scope).
- A non-lawyer is being given pack access — the role capture drives the attorney gate everywhere downstream.
Do NOT use it to perform a review (route to the review skills) or to store per-matter state (the pack deliberately ships no matter-workspace).
Procedure
Step 0: Offer quick vs full
- Quick (≈2 min) — jurisdiction, role, escalation owner. Writes
[DEFAULT]markers for everything else and tells the user which to tune later. - Full (≈15 min) — adds playbook positions per skill (NDA terms, contract clause stances, DPA sub-processor / audit / liability positions). Pause/resume via a
<!-- PROFILE PAUSED AT: <section> -->marker +[PENDING]fields.
Step 1: Capture the load-bearing identity
- Jurisdiction — must be within EU/DE scope. If the user names an out-of-scope jurisdiction, surface the hard-refusal: the pack covers EU/DE only; for others, consult licensed local counsel. Record the chosen jurisdiction; every skill stamps it as its
Jurisdiction:tag. - Role — lawyer / non-lawyer-with-access / non-lawyer-without. This is load-bearing: it selects the work-product header and arms the GREEN×non-lawyer attorney gate in every skill. Capture honestly; never infer.
- Escalation owner + reviewer — who the attorney gate routes to, who signs off RED items.
Step 2: Capture playbook positions (full mode) — in plain prose, never YAML the user edits
What ships with it
1 file 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.
- 8d ago First seen · 228 lines · 44 tokens per session scan A 7d577b61dae0
legal-practice-profile is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 3,053 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
telnyx-email-suppressions-curl
Manage email suppressions (blocks), import and export suppression lists, and manage unsubscribe groups. Use for deliverability compliance and bounce handling.
healthcare-providers-verify
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these…
python-packaging-license-finder
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.
patent-review
Multi-round cyclic rigorous review of Chinese patent technical disclosure documents. Supports multi-dimension review (data flow closure, terminology consistency, state transition, formula completeness, error code routing, text-diagram consistency), round-by-round convergence, and optional auto-fix (default off, severe…
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.