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 transition-services-agreement-reviewgit 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/transition-services-agreement-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/transition-services-agreement-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/transition-services-agreement-review/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/transition-services-agreement-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/transition-services-agreement-review.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.00073 | $0.04337 |
| Opus 5 | $0.00036 | $0.02168 |
| Sonnet 5 | $0.00015 | $0.00867 |
| Haiku 4.5 | $0.00007 | $0.00434 |
Grade A, and why
Transition Services Agreement Review 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transition Services Agreement Review
Purpose
Review a draft or executed transition services agreement (TSA) — the agreement under which a seller or parent continues to provide operational services (IT, finance, HR, facilities, and similar functions) to a divested business, or a buyer provides services back to a seller, for a defined period after closing. The skill checks the service schedules for completeness against the stated deal perimeter, reviews service standards and duration/termination mechanics, records pricing and cost-plus terms, reviews IP/data/systems-access provisions, checks the TSA's consistency with the purchase agreement, and reviews exit/migration obligations and any reverse-TSA terms.
This skill produces draft work product for attorney review only. It is not legal advice and is not a determination that the TSA is complete, adequately priced, or ready to sign. Whether a service is priced fairly, whether a term is enforceable, and whether the TSA is ready to execute are attorney and business-team decisions — this skill organizes the review and flags the questions; it does not answer them.
Use When
- A buyer or seller's deal team has a draft TSA (or a term sheet for one) and needs it checked against the deal perimeter before signing.
- The service schedules need to be checked for completeness — whether every function the target relies on during the transition is actually scheduled and priced.
- The TSA's duration, extension, and early-termination mechanics need review, including whether they align with the buyer's stand-up or migration plan.
- The TSA's pricing and cost-plus mechanics need to be recorded and checked for consistency and for unpriced gaps.
- The TSA needs to be checked against the purchase agreement for consistent definitions, entities, and indemnity treatment.
- A reverse TSA (buyer providing services back to seller) is part of the deal and needs the same review from the other direction.
Required Inputs
- The TSA text — the full draft or executed transition services agreement, including all service schedules and exhibits, uploaded or pasted. Do not review from a summary or a partial excerpt.
- The purchase agreement and the stated deal perimeter — what business, assets, and entities are being transferred, so the service schedules can be checked against what the recipient will actually need. Without the perimeter definition, completeness cannot be assessed and the gap is flagged, not guessed at.
- The side the review is for — service provider or service recipient — and, for a carve-out, whether the recipient is the buyer or a newly separated entity.
- Optional: disclosure schedules and diligence functional workstream lists — used to cross-check which functions diligence identified as transition-critical.
- Optional: prior transition planning materials (e.g., a functional separation plan, an IT systems inventory) — used to check the service schedules against what the business actually depends on.
- Jurisdiction and governing law — as stated in the TSA, or flagged as unknown.
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 · 163 lines · 73 tokens per session scan A e3f765adebe5
Transition Services Agreement Review is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 4,337 once invoked, about $0.0004 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.