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 zgbrenner/agentcounsel --skill privilege-log-reviewgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/privilege-log-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/privilege-log-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/privilege-log-review/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/zgbrenner/agentcounsel/privilege-log-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/privilege-log-review.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.00049 | $0.02803 |
| Opus 5.5 | $0.00020 | $0.01121 |
| Sonnet 5.5 | $0.00010 | $0.00561 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
Privilege Log Review 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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privilege Log Review
Purpose
Produce a structured, attorney-ready first-pass review of a privilege log. The skill sorts each log entry into one of three tiers — confidently privileged, uncertain and flagged for attorney decision, or recommend-remove — and surfaces patterns, format deficiencies, and anomalies. It does not make final privilege calls, strip designations, or decide what to produce or withhold. That judgment belongs to the attorney. The output is draft legal work product for attorney review — not legal advice.
Use When
- Counsel needs a first-pass triage of a privilege log before conducting a detailed privilege review.
- A privilege log has been received from opposing counsel and counsel wants a structured analysis before a meet-and-confer or motion challenge.
- A party is preparing its own privilege log and wants a quality-control pass to identify thin descriptions, format deficiencies, and likely-challengeable designations before service.
- A large log needs to be organized so attorney review time is concentrated on the close calls rather than the clear cases.
Required Inputs
- The full privilege log. Each entry must contain at minimum: date, author, recipients (To / CC / BCC), document type, privilege claimed, and description. If any of these fields are missing across entries, note those entries as format-deficient and proceed with what is available.
- The matter name and number.
- The forum and jurisdiction (court, arbitral body, or regulatory proceeding). If not provided, stop and request it; the applicable privilege rule varies by forum.
- The applicable privilege rule text, if available (e.g., a local rule, standing order, or agreed ESI protocol specifying log format and required fields). If not provided, flag as
[CONFIRM: applicable privilege log rule — verify with counsel]and proceed using the required-fields list above as the baseline. - Whether any underlying documents are available for spot-check purposes. If so, identify which entries will be spot-checked; do not review underlying documents beyond the scope provided.
- Whether any use-restriction order or clawback agreement is in effect that limits how the log or its contents may be used.
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.
- 1mo ago First seen · 124 lines · 49 tokens per session scan A cd935614f128
Privilege Log Review is a skill published in the GitHub repository zgbrenner/agentcounsel (21 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 2,803 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
mqc-chronicle-master
A document-preparation workflow that turns a collection of legal materials into a dated case timeline. It copies facts from the source, records dates, parties, page references, and conflicts, and produces Word, Excel, and a short visual version.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
treatment-plans
Formats and structurally validates local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
fill-icmje-coi
Use when each author needs an ICMJE Conflict of Interest disclosure form (coidisclosure.docx) for submission. Clones a pre-filled synthetic seed with every item marked None and replaces only date, name and manuscript title, so most authors just confirm or amend.
cowork-data-room-builder
Prepare YOUR data room for a fundraise, acquisition, or bank diligence -- builds the checklist for your deal stage, sweeps your folders for what you already have, produces a gap report, and organizes everything into the structure buyers and investors expect. The sell-side complement to cowork-deal-room.
software-copyright
A guided workflow for preparing Chinese software copyright registration materials from a real software project. It produces drafts such as application details, source-code documents, and a user manual.