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 privilege-log-review-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/privilege-log-review-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/privilege-log-review-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/privilege-log-review-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/privilege-log-review-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/privilege-log-review-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.00143 | $0.04556 |
| Opus 5.5 | $0.00057 | $0.01822 |
| Sonnet 5.5 | $0.00029 | $0.00911 |
| Haiku 4.5 | $0.00014 | $0.00456 |
Grade A, and why
privilege-log-review-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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/privilege-log-review
Note on terminology. This skill keeps the US name "privilege log" because that's the plugin's file/command name, but Brazilian civil procedure has no broad discovery obligation and no standard cataloged log of withheld documents. The functional equivalent arises only when a court orders exibição de documento ou coisa (CPC arts. 396-404) and the responding party invokes a ground to refuse — most commonly sigilo profissional do advogado under CPC art. 404 combined with the Estatuto da OAB (Lei 8.906/1994) art. 7º, XIX. This skill reviews that justificativa de recusa de exibição entry by entry, applying the same underlying discipline (defend which documents are properly withheld and why) mapped onto the real BR mechanism.
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ review protocol, format of the justificativa de recusa. - Follow the workflow and reference below.
- For each entry: obvious sigilo / obvious not sigilo / needs attorney review. Flag reasons.
- Output: reviewed justificativa with flags. Attorney reviews all flags before responding to the order for exibição.
Review of Justificativa de Recusa de Exibição (sigilo profissional)
Disclosed-document use restrictions
Before working with a set of litigation documents, ask: "Were any of these documents obtained through disclosure or discovery in legal proceedings?" If yes:
- England & Wales (CPR 31.22): Documents obtained through disclosure are subject to the implied undertaking — you may only use them for the purpose of the proceedings in which they were disclosed, unless the court grants permission, the disclosing party consents, or the document has been read in open court. Using them for a different matter, a different claim, or a commercial purpose without permission is a contempt.
- US: Protective orders and Rule 26(c) may impose similar restrictions. Check the order.
- Other jurisdictions: Similar restrictions commonly apply. Check the local rule.
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 8b07a0948e68
- 26d ago First seen · 240 lines · 143 tokens per session scan A 267b0efd17d6
privilege-log-review-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 143 tokens to every session and 4,556 once invoked, about $0.0006 per session on Opus 5.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-10-02.
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…