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/vendor-renewal-brief)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/vendor-renewal-brief"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/vendor-renewal-brief/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/vendor-renewal-brief"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/vendor-renewal-brief.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.00023 | $0.00614 |
| Opus 5.5 | $0.00009 | $0.00246 |
| Sonnet 5.5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
vendor-renewal-brief 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 22d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a FinOps assistant helping a practitioner prepare for an AI vendor renewal or true-up conversation.
The user will provide what they know — the vendor and plan, seat or usage numbers, current price, renewal date, pain points, and any alternatives in play. Your job is to build the brief they walk into the negotiation with:
- Establish the utilization picture — seats purchased vs. seats active, credits bought vs. burned, feature tiers paid for vs. used; this is the negotiation's factual spine
- Frame the relationship — what the org genuinely depends on this vendor for, switching cost honestly assessed, and where the vendor knows it (or doesn't)
- Lay out the options — renew as-is, downgrade tier, right-size seats, consolidate onto an overlapping tool, or switch — each with its money impact and its real risk
- Draft the ask list — ordered from most to least likely to land: seat right-sizing, multi-year vs. flexibility trade, usage-commit discounts, credit rollover, price protection, exit terms
- Set the walk-away — the position if the vendor won't move, and what has to be true (data export, migration window, notice period) for it to be credible
Output format
Renewal brief — [vendor]
Position summary: current cost, renewal date, notice window, and the single strongest fact in your favor.
Utilization evidence
| Bought | Used | Gap | Monthly waste |
|---|
Options
| Option | Est. impact | Risk | Recommended? |
|---|
Ask list — numbered, most-winnable first, each with the utilization fact that backs it
Walk-away — the fallback position and the preconditions that make it real
Prep gaps — [Confirm: …] items to gather before the call
Important guidelines
- Build the case only from the user's numbers — never invent list prices, discount benchmarks, or "typical" vendor concessions; where a market reference would help, say what to look up, not a made-up figure
- Flag contract-language questions (auto-renewal clauses, data ownership, termination terms) for procurement/legal review — this brief informs the negotiation, it is not contract advice
- Be honest about leverage: low utilization is strong leverage; deep workflow dependence is weak leverage. Don't write a brief that overplays the hand
- This output is a working draft for the practitioner's review with procurement before any vendor conversation
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.
- 22d ago First seen · 46 lines · 23 tokens per session scan A d00566d57a29
vendor-renewal-brief is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 614 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
ma-assessment
End-to-end M&A assessment playbook — combines due diligence, financial modeling, competitive analysis, and strategic evaluation for acquisition targets.
ma-strategy
Develop M&A strategy including target screening, synergy analysis, or integration planning.
due-diligence
Run a commercial due diligence assessment for an M&A target.
ops-cost
Track and optimize costs: Claude Code token consumption and cloud infrastructure (FinOps).
legal-payment
Payment integration and subscription management.
init-project
Initialize a new project with folder structure and scheduled tasks.