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 ThomasMoreAI/legal-skills-open --skill reg-gap-analysis-privacy-legal-bossmann007git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/reg-gap-analysis-privacy-legal-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/reg-gap-analysis-privacy-legal-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/reg-gap-analysis-privacy-legal-bossmann007/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/thomasmoreai/legal-skills-open/reg-gap-analysis-privacy-legal-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/reg-gap-analysis-privacy-legal-bossmann007.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.00088 | $0.02635 |
| Opus 5.5 | $0.00035 | $0.01054 |
| Sonnet 5.5 | $0.00018 | $0.00527 |
| Haiku 4.5 | $0.00009 | $0.00264 |
Grade A, and why
reg-gap-analysis-privacy-legal-bossmann007 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 24d 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.
This is a copy
98% identical to reg-gap-analysis-bossmann007 — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reg-gap-analysis
- Load
~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md→ privacy policy commitments, regulatory footprint, DSAR systems. - Run the workflow below.
- Scope: does the regulation apply? (jurisdiction, thresholds, sector)
- Extract requirements → diff against current state → gap list.
- Remediation plan with owners, dates, prioritization.
- Save dated doc. Even "no gaps" gets documented.
/privacy-legal:reg-gap-analysis "Resolução CD/ANPD nº 15/2024"
/privacy-legal:reg-gap-analysis
[paste guidance / reg text]
Regulation-to-Policy Gap Analysis
Purpose
The ANPD issues new guidance or a Resolução CD/ANPD. A sectoral regulator (BCB, ANVISA, ANS) finalizes a rule touching personal data. The ICO or another foreign DPA issues guidance relevant to a cross-border footprint. Something moves — and now you need to know what, if anything, you have to change.
This skill diffs the new requirement against what you currently do (per ~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md → Privacy policy commitments + the practices documented in PIAs) and produces a gap list with a remediation plan.
Load current state
Read ~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md:
## Privacy policy commitments— what you've publicly promised## Regulatory footprint— what already applies## DSAR process→ systems list — what you actually do operationally
If the regulation doesn't apply to you (wrong jurisdiction, below threshold, different sector), the gap analysis is one line: "Doesn't apply. Here's why: [reason]. No action needed."
Workflow
Step 1: Scope the regulation
Before diffing, answer:
- Does it apply? Jurisdiction (do you have data subjects there?), threshold (revenue, user count, data volume), sector carve-outs
- When? Effective date, enforcement date (often later), any phase-in
- What's actually new? Brazil has a single national framework (LGPD), not a state-by-state patchwork — a simpler regulatory map than jurisdictions with dozens of overlapping state laws. Most "new" developments are ANPD Resoluções refining an existing LGPD provision, or a sectoral regulator (BCB, ANVISA, ANS) layering a rule on top of LGPD, not a wholesale new regime. Identify the delta from what you already comply with under LGPD, not the full text.
What ships with it
2 files 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.
- 24d ago First seen · 189 lines · 88 tokens per session scan A a9e21d508aef
reg-gap-analysis-privacy-legal-bossmann007 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 88 tokens to every session and 2,635 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to reg-gap-analysis-bossmann007, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…