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 post-closing-obligations-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/post-closing-obligations-tracker)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/post-closing-obligations-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/post-closing-obligations-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/post-closing-obligations-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/post-closing-obligations-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.00040 | $0.02629 |
| Opus 5 | $0.00020 | $0.01314 |
| Sonnet 5 | $0.00008 | $0.00526 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade A, and why
Post-Closing Obligations 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Closing Obligations Tracker
Purpose
Extract the post-closing covenants and obligations from an executed or near-final M&A acquisition agreement and its ancillary documents, and organize them — from a stated side of the deal — into a single tracked obligation list, with a source citation for every obligation and a flag on anything the documents leave unstated.
This skill produces draft work product for attorney review only. It is not legal advice and is not a determination that any obligation has been satisfied, waived, or breached. The acquisition agreement and the ancillary documents control; this tracker only restates what they say so an attorney and a deal team can monitor performance.
Use When
- A user asks to "build a post-closing tracker," "list the post-closing covenants," "what do we still owe after closing," or "what does the seller still have to do."
- A deal team needs a structured, source-cited list of post-closing obligations to monitor performance after a signed or closed acquisition.
- The post-closing covenants of an acquisition, merger, asset purchase, stock purchase, or membership-interest purchase must be organized for tracking.
Required Inputs
- The acquisition agreement text — uploaded or pasted. Do not extract from a description, a summary, or a partial excerpt.
- The ancillary documents — for example an escrow agreement, transition services agreement, employment or non-competition agreements, an earnout schedule, IP assignments, or disclosure schedules — uploaded or pasted if they exist. Note any that are referenced but not provided.
- The side the tracker is for — buyer-side or seller-side.
- The deal type — for example a stock purchase, asset purchase, merger, or membership-interest purchase.
- The closing date and any other key dates — as stated by the user or in the documents, or flagged as unknown. Dates are never computed.
- Jurisdiction and governing law — as stated in the documents, or flagged as unknown.
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 · 223 lines · 40 tokens per session scan A db329e82a868
Post-Closing Obligations Tracker is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 2,629 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.