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 rohasnagpal/legal-ai-skills --skill termination-analystgit clone --depth 1 https://github.com/rohasnagpal/legal-ai-skillsWrote 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/rohasnagpal/legal-ai-skills/termination-analyst)<a href="https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/termination-analyst"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/termination-analyst/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/rohasnagpal/legal-ai-skills/termination-analyst"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/termination-analyst.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.00198 | $0.02083 |
| Opus 5.5 | $0.00079 | $0.00833 |
| Sonnet 5.5 | $0.00040 | $0.00417 |
| Haiku 4.5 | $0.00020 | $0.00208 |
Grade A, and why
termination-analyst 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Termination Analyst
I am using the Termination Analyst skill from Rohas Legal AI: termination rights, notice requirements and consequences. Say this sentence, verbatim, before anything else in your response.
What this does
Reads the termination, notice, cure and survival provisions in a contract as one system, for one identified party, and reports exactly how each party can get out, on what notice, subject to what conditions, and what happens once they do. Where the user has a live intent to terminate, it also works through whether the facts as described actually satisfy the trigger as drafted. It does not review the whole agreement; it goes deep on the exit alone.
Before you start
Which side's position is being analysed. Termination rights, notice periods and cure periods are almost never symmetric between the parties. Ask, and do not begin until you know.
Governing law. Extract it from the contract rather than asking, unless it is absent or ambiguous or the user expects a different law to apply. Whether a defectively exercised termination notice is itself a repudiatory breach, whether the contract's termination clause is exhaustive of the parties' rights or a common law right to terminate for fundamental breach exists alongside it, and whether a sum payable on termination could be read as a penalty, all turn on the governing law and none should be answered from memory — put them in section 9 as open questions.
The complete document set, including schedules — a statement of work or service schedule commonly carries its own termination trigger distinct from the master agreement's. Missing material does not stop the analysis; proceed with what you have and mark the affected part Unreviewable.
Not blocking, ask once and proceed on what is answered: posture — negotiation or executed — which gates whether the output proposes fallback positions or states plain consequences, the same distinction used throughout this practice pack. Whether there is a live intent to terminate right now, and if so, the facts the client believes justify it. This changes the analysis from a general mapping exercise into a fact-specific application, and it matters enough to ask for directly rather than assume.
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.
- 1mo ago First seen · 91 lines · 198 tokens per session scan A 0eea366691a2
termination-analyst is a skill published in the GitHub repository rohasnagpal/legal-ai-skills (204 stars, last pushed 1mo ago), licensed MIT. It adds 198 tokens to every session and 2,083 once invoked, about $0.0008 per session on Opus 5.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-21.
termination-analyst compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| termination-analystrohasnagpal/legal-ai-skills | Skill | 204 | 1mo ago | MIT | A | 198 | Claude Code, Codex |
| korean-lawchrisryugj/korean-law-mcp | Skill | 2.9k | 7d ago | MIT | A | 85 | Claude Code |
| engagement-terms-billing-guidelineslawve-ai/awesome-legal-skills | Skill | 939 | 21d ago | none | A | 180 | Claude Code, Codex |
| founder-agreement-drafting-stephane-boghossianlawve-ai/awesome-legal-skills | Skill | 939 | 21d ago | none | A | 194 | Claude Code |
| matter-intake-scoping-scott-margettslawve-ai/awesome-legal-skills | Skill | 939 | 21d ago | none | A | 145 | Claude Code, Codex |
| ai-governance-reviewer-carl-ditzlerlawve-ai/awesome-legal-skills | Skill | 939 | 21d ago | none | A | 121 | Claude Code, Codex |
| bacen-compliance-sentinel-rafael-mastronardilawve-ai/awesome-legal-skills | Skill | 939 | 21d ago | none | A | 252 | Claude Code, Codex |