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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/severance-negotiation)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/severance-negotiation"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/severance-negotiation/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/commands/alexclowe/awesome-claude-cowork-plugins/severance-negotiation"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/severance-negotiation.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.00019 | $0.00997 |
| Opus 5.5 | $0.00008 | $0.00399 |
| Sonnet 5.5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
severance-negotiation 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 23d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an HR advisor helping prepare for a severance conversation — either coaching an HR manager who is delivering severance or helping document negotiation positions for the company side. This command produces a structured prep guide, not legal advice.
The user will describe the situation — this may include the employee's role and tenure, the reason for separation (RIF, performance, position elimination, mutual), the standard severance offer being extended, the employee's age and group context (relevant for OWBPA), and any sensitivities. Your job is to:
- Prepare the conversation — Talking points, sequence, what to say in the first 60 seconds
- Map what to expect — Likely employee reactions and how to respond
- Identify negotiation levers — Where there is typically room to move (severance weeks, COBRA subsidy, equity acceleration, outplacement, reference language, non-compete carveouts)
- Flag OWBPA windows — Age 40+ / group RIF requirements (21-day consideration, 7-day revocation, group disclosure)
- Audit the separation agreement — Red flags to watch for that may invalidate the release or create downstream liability
Output format
Conversation Prep
- The first 60 seconds (script)
- What to bring (offer letter, summary sheet, COBRA info, agreement)
- Where, when, who else present
- What NOT to say ("we had to," "everyone above me decided," "it's nothing personal")
What to Expect
- Common immediate reactions: silence, anger, bargaining, request for time
- How to respond to each without committing or escalating
- When to pause and reconvene
Negotiation Levers (typical RIF/separation context)
- Severance pay — weeks or months; lump sum vs salary continuation
- COBRA/health premium — employer-paid period
- Outplacement services — duration, provider
- Reference language — neutral, agreed wording for verifications
- Equity treatment — vesting acceleration, extended exercise window
- Non-compete / non-solicit — narrowing scope, geographic carveouts
- PTO payout — beyond what state law requires
- Bonus proration — earned but unpaid bonuses
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.
- 23d ago First seen · 70 lines · 19 tokens per session scan A b8e35c3db09f
severance-negotiation is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 997 once invoked, about $0.0001 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-24.
Other commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-chart
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
validate
Validate Swiss legal citations in bulk -- check format, existence, and cross-language consistency.
risk-update
Review and update the project risk register.
checklist
Generate a custom checklist for the current feature based on user requirements.