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 termination-riskgit 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/termination-risk)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/termination-risk"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/termination-risk/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/termination-risk"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/termination-risk.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.00027 | $0.03153 |
| Opus 5 | $0.00014 | $0.01577 |
| Sonnet 5 | $0.00005 | $0.00631 |
| Haiku 4.5 | $0.00003 | $0.00315 |
Grade A, and why
Termination Risk 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Termination Risk
Purpose
Produce a structured, attorney-ready fact-and-risk summary for a proposed employee termination. The skill organizes available facts, surfaces risk factors, and generates a checklist for attorney review. It does NOT decide whether the termination is lawful, evaluate jurisdiction-specific statutes, or substitute for employment counsel. This is draft legal work product — not legal advice.
Use When
- A manager or HR professional is preparing to terminate an employee and wants to surface legal risk factors before proceeding.
- An attorney needs a structured intake of termination facts to begin their risk assessment.
- A user says "we want to let someone go — what should we be thinking about?" or "help me think through the risk of this termination."
- A separation is being planned in the context of a reduction in force, performance management conclusion, or misconduct investigation.
- The user needs to organize documentation in advance of a termination meeting.
Required Inputs
- Employee identifier: a role description or anonymized identifier. Do not use the employee's real name in reusable templates.
- Employment status: at-will, fixed-term contract, collective bargaining agreement, or unknown. If unknown, flag for attorney confirmation.
- Stated reason for termination: the specific reason the employer intends to assert (e.g., performance, misconduct, position elimination, restructuring).
- Documentation history: what written documentation exists — performance improvement plans, written warnings, investigation reports, or records showing the business reason.
- Tenure and role: length of employment, job title or level, and reporting structure.
If any required input is missing, stop and request it before proceeding. Do not fabricate facts, documentation status, or employment terms.
Do Not Use When
- The termination has already occurred and the question is how to respond to a filed claim or charge — that is separate, attorney-directed litigation-response work, not covered by this skill.
- The user is asking to draft the termination letter itself rather than assess risk (a separate drafting skill applies).
- The question is whether a worker should be classified as an employee or an independent contractor (use
worker-classification). - The employee being considered for termination is on, has recently taken, or has recently returned from protected leave (medical/family, military/service, disability-accommodation, or similar), and the primary question is the leave-specific interference or retaliation exposure — use
protected-leave-reviewfor that analysis. This skill organizes the overall termination picture;protected-leave-reviewhandles the leave-specific deep-dive. - A wage-and-hour question has surfaced — including whether the employee was correctly classified as exempt or non-exempt, or whether there is back-pay exposure — use
wage-hour-qafor that analysis. This skill does not analyze pay classification or compute back-pay figures. - The user needs jurisdiction-specific legal conclusions about lawfulness — this skill provides workflow discipline, not legal opinions.
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 · 148 lines · 27 tokens per session scan A 4ce41f436eaa
Termination Risk is a skill published in the GitHub repository zgbrenner/agentcounsel (18 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 3,153 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.