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 integration-legal-issues-checklistgit 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/integration-legal-issues-checklist)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/integration-legal-issues-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/integration-legal-issues-checklist/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/integration-legal-issues-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/integration-legal-issues-checklist.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.00031 | $0.02852 |
| Opus 5 | $0.00015 | $0.01426 |
| Sonnet 5 | $0.00006 | $0.00570 |
| Haiku 4.5 | $0.00003 | $0.00285 |
Grade A, and why
Integration Legal Issues Checklist 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Legal Issues Checklist
Purpose
Generate a structured legal integration checklist for a merger or acquisition after signing or closing, organized by workstream so legal and business owners can see, in one place, the integration tasks that carry a legal dimension, who owns each, and which items must be escalated.
This skill produces draft work product for attorney review only. It is not legal advice, not an integration plan, and not a determination of what the law requires. Integration touches HR, tax, antitrust, regulatory, and employment questions that belong to the responsible attorneys and specialists; this checklist is a process scaffold those professionals adapt and own.
Use When
- A user asks to "build an integration checklist," "list the legal issues for integration," or "what legal tasks do we need to track after signing or closing."
- A deal team needs a workstream-organized view of the legal integration tasks for a signed or closing M&A transaction.
- A legal and business team needs a shared scaffold that assigns owners and flags escalation items across entity, governance, contracts, employment, IP, privacy, regulatory, litigation, insurance, real estate, records, tax, and policy workstreams.
Required Inputs
- The deal type and structure — for example a stock purchase, asset purchase, merger, membership-interest purchase, or carve-out — and the legal structure of the combination.
- Whether the matter is pre-close or post-close — signed but not yet closed, or already closed. This changes which workstreams apply and how antitrust clean-team boundaries are treated.
- The target profile — for example the target's size, locations, business lines, and whether it is regulated, unionized, or publicly traded — at the level of detail the user can provide.
- The side the checklist is prepared for — buyer-side, seller-side, or the combined entity.
- Jurisdiction and governing law — as stated for the deal, or flagged as unknown.
- The document set available — for example the definitive agreement, disclosure schedules, the diligence report, or an integration plan — if any.
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 · 243 lines · 31 tokens per session scan A 5d47755f4507
Integration Legal Issues Checklist is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 2,852 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…
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.
claims-documentation
Document construction claims for disputes and recovery. Compile evidence, calculate damages, track notice requirements, and prepare claim packages.
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.