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 redline-summarygit 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/redline-summary)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/redline-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/redline-summary/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/redline-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/redline-summary.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.00052 | $0.03431 |
| Opus 5 | $0.00026 | $0.01716 |
| Sonnet 5 | $0.00010 | $0.00686 |
| Haiku 4.5 | $0.00005 | $0.00343 |
Grade A, and why
Redline Summary 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 9d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redline Summary
Purpose
Produce a structured, attorney-ready summary of the substantive edits between two versions of a contract, or within a single document containing tracked changes, or across a base agreement and a series of amendments. For each change, this skill identifies what was modified, which party the change favors, whether the change is material, and whether it warrants pushback or further negotiation. When an amendment chain is provided, the skill also establishes the chronological order of the documents and traces how the agreement has evolved across the entire chain. It produces draft legal work product for attorney review only. It is not legal advice and does not constitute a final negotiating position.
The core discipline of this skill: report only edits that are actually present in the provided documents. Do not invent, interpolate, or assume changes that are not visible in the text. Do not characterize a change as "standard" or "acceptable" without flagging that characterization for attorney confirmation.
Use When
- A counterparty has returned a redlined draft and the user needs a structured summary of what changed.
- The user asks to "summarize the redlines," "what did they change," "walk me through the markups," or "what should I push back on."
- The user has two versions of a contract (clean or tracked) and needs to understand what is different between them.
- Negotiations have progressed through multiple rounds and the user needs a record of which issues have moved and which remain open.
- An in-house team needs a quick summary of outside counsel redlines before a negotiation call.
- The user wants to compare a counterparty's proposed edits against the client's original draft to assess concession patterns.
- The user has a base agreement plus one or more amendments and needs to understand how the contract has evolved across the full amendment history.
- The user needs to trace a specific provision through multiple amendments to determine its current controlling language.
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.
- 9d ago First seen · 159 lines · 52 tokens per session scan A 80a87ba9be43
Redline Summary is a skill published in the GitHub repository zgbrenner/agentcounsel (18 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 3,431 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
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
Format and structurally validate 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
Batch-generate per-author ICMJE Conflict of Interest Disclosure Forms (coidisclosure.docx) for manuscript submission. Pre-fills all 13 disclosure items as "☒ None" + final certification ☒ using a synthetic seed template shipped with the skill, then clones the seed per author with Date, Name, and Manuscript Title…
law-to-markdown
A legal-document conversion skill for turning PDF, Word, or plain-text regulations into structured Markdown. Markdown is a text format that uses simple symbols for headings and lists.
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.
legaltech-expert
Expert in legal technology: contract lifecycle management, e-discovery, AI-assisted legal research, case and matter management, document automation, and compliance tooling. Use when the user mentions legal case or matter management, e-discovery and legal holds, CLM or contract review and obligation tracking, legal…