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 legal-meeting-briefinggit 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/legal-meeting-briefing)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/legal-meeting-briefing"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/legal-meeting-briefing/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/legal-meeting-briefing"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/legal-meeting-briefing.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.02021 |
| Opus 5 | $0.00024 | $0.01010 |
| Sonnet 5 | $0.00010 | $0.00404 |
| Haiku 4.5 | $0.00005 | $0.00202 |
Grade A, and why
Legal Meeting Briefing 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 8d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legal Meeting Briefing
Purpose
Produce a structured, review-ready draft briefing for a meeting with legal relevance — a deal review, a board or committee meeting, a vendor call, a regulatory meeting, a litigation discussion, or a cross-functional meeting. The briefing organizes background, participants, agenda, key documents, open issues, legal considerations, talking points, questions, and decisions needed, and sets up a tracker for the action items the meeting produces.
This skill provides workflow discipline and structure. It produces draft work product for review. This is not legal advice. A briefing organizes information for a meeting; it does not decide the legal questions the meeting will address.
Use When
- A user says "prepare me for this meeting," "build a briefing for this board meeting," or "get me ready for this negotiation."
- A legal team member needs a structured briefing pack before a meeting with legal relevance.
- The user needs a way to capture and track the action items that come out of a meeting.
Required Inputs
- Meeting context: the meeting title and type, date and time, the participants and their roles, the agenda or expected topics, and the legal team member's role in the meeting (advisor, presenter, negotiator, observer).
- Background materials: the documents and records the user provides — prior correspondence, prior meeting notes, relevant agreements, matter records, the risk register, or deal documents. The skill briefs from the materials supplied; it does not pull information from calendars, email, CRM, CLM, or other external systems.
- Negotiation parameters (for a negotiation meeting): the red lines or non-negotiable positions, if any have been set.
If the meeting context is missing, request it. If background materials are thin, proceed and flag the resulting preparation gaps explicitly.
Do Not Use When
- The user expects the agent to fetch information from a calendar, email, CRM, CLM, or other connected system — this skill briefs only from materials the user supplies.
- The meeting requires a substantive legal position to be decided before it happens — that is attorney work, not a briefing; route it to the relevant practice-area skill or an attorney.
- The task is to draft a board resolution or written consent — use
written-consentorboard-minutes.
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.
- 8d ago First seen · 146 lines · 49 tokens per session scan A 01c2435f8584
Legal Meeting Briefing is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 2,021 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.
safety-inspection-checklist
Digital safety inspection checklists for construction sites. Generate, conduct, and track safety inspections with automated reporting and compliance monitoring.
delay-analysis
Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes.
change-order-manager
Manage construction change orders from request to approval. Track costs, schedule impacts, and maintain audit trail for dispute prevention.