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 closing-deliverables-trackergit 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/closing-deliverables-tracker)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/closing-deliverables-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/closing-deliverables-tracker/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/closing-deliverables-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/closing-deliverables-tracker.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.00036 | $0.02621 |
| Opus 5 | $0.00018 | $0.01311 |
| Sonnet 5 | $0.00007 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
M&A Closing Deliverables Tracker 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
M&A Closing Deliverables Tracker
Purpose
Build a closing-deliverables tracker for a merger, acquisition, or strategic investment: a structured checklist of the documents, certificates, consents, and other items the parties need to assemble, sign, and deliver to close the deal. The tracker organizes each deliverable by responsible party and records its status, dependencies, source, signer, and any execution-formality needs.
This skill produces draft work product for attorney review only. It is not legal advice and is not a determination that a deal is ready to close. The tracker is a project-management aid; the deal team and counsel decide what the transaction actually requires.
Use When
- A user asks to "build a closing checklist," "make a closing-deliverables tracker," "what do we need to close," or "who is responsible for each closing document."
- A deal team needs a structured tracker to drive a merger, acquisition, asset purchase, stock purchase, or membership-interest purchase toward closing.
- A purchase agreement has been signed and the closing-conditions and deliverables provisions must be turned into a working checklist.
Required Inputs
- The deal type — for example a stock purchase, asset purchase, merger, membership-interest purchase, or strategic investment.
- The side the tracker is built for — buyer-side, seller-side, company-side, or joint deal-team use.
- The transaction stage — for example pre-signing, signed and pending closing, or at the closing — since the stage shapes which deliverables are still open.
- The parties involved — buyer, seller, the target or company, the escrow agent, and any lender or other financing source.
- The purchase agreement and any ancillary documents — uploaded or pasted, if they exist. The closing-conditions and closing-deliverables sections drive the most accurate tracker.
- Jurisdiction and governing law — as stated in the agreement, or flagged as unknown.
- Any user-supplied dates — a target closing date or a known filing window — recorded as supplied and flagged for verification.
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 · 233 lines · 36 tokens per session scan A 776bfdc9bed8
M&A Closing Deliverables Tracker is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,621 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.