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 dsar-response-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/dsar-response-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/dsar-response-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/dsar-response-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/dsar-response-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/dsar-response-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.00144 | $0.04838 |
| Opus 5.5 | $0.00058 | $0.01935 |
| Sonnet 5.5 | $0.00029 | $0.00968 |
| Haiku 4.5 | $0.00014 | $0.00484 |
Grade A, and why
dsar-response-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
86% identical to dsar-response — 30 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dsar-response
- Load
~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md→ DSAR process (systems list, verification method, SLA). - Run the workflow below.
- Classify request type. Check escalation triggers — if any fire, route before proceeding.
- Walk through: verify identity → walk systems list → exemption analysis → draft.
- Output response draft. Do NOT send — human reviews and sends.
- Log the DSAR per house process.
Before pasting the request: the request will contain the data subject's PII. Confirm your session and output storage meet your data-handling requirements. Redact anything you don't need (ID attachments, unrelated email threads). Do not store the subject's name in filenames.
/privacy-legal:dsar-response
[paste the request email]
DSAR Response Drafting
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /privacy-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/privacy-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
A DSAR has a deadline (set by the applicable regime), a process (verify, locate, assess exemptions, respond), and a bunch of places it can go wrong. This skill walks through each step and drafts the response.
Premissa de jurisdição
Esta análise assume a LGPD (Lei 13.709/2018) como base, com os direitos do titular do Art. 18: I - confirmação da existência de tratamento; II - acesso aos dados; III - correção de dados incompletos/inexatos/desatualizados; IV - anonimização, bloqueio ou eliminação de dados desnecessários/excessivos/tratados em desconformidade; V - portabilidade a outro fornecedor de serviço; VI - eliminação de dados tratados com consentimento (ressalvado Art. 16); VII - informação sobre entidades públicas/privadas com quem os dados foram compartilhados; VIII - informação sobre a possibilidade de não fornecer consentimento e as consequências; IX - revogação do consentimento (Art. 8º, §5º). Para confirmação de existência de tratamento e acesso, a lei estabelece prazo de 15 dias (LGPD art. 19, II) — prazo legal e obrigatório [settled — last confirmed 2026-07-02]. Para os demais direitos do Art. 18 (correção, anonimização, bloqueio, eliminação, portabilidade, revogação), cabendo à empresa definir prazo razoável em sua CLAUDE.md de configuração (referência de mercado: 15 dias corridos, prorrogável uma vez mediante justificativa comunicada ao titular). Diferente do GDPR (30 dias) ou CCPA (45 dias), a LGPD não prescinde estatutariamente para os direitos além de confirmação/acesso. Se o titular, a atividade de tratamento, ou o controlador estiver sujeito a outra jurisdição além do Brasil (ex.: titular na UE → GDPR se aplica cumulativamente), sinalizar isso e não aplicar apenas o framework LGPD.
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 Changed 4f4e61dc56f9
- 26d ago First seen · 291 lines · 144 tokens per session scan A fdd815928ffe
dsar-response-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 144 tokens to every session and 4,838 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to dsar-response, differing in 30 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…