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 cnfeat/top-pm-skills --skill renewal-playbookgit clone --depth 1 https://github.com/cnfeat/top-pm-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/cnfeat/top-pm-skills/renewal-playbook)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/renewal-playbook"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/renewal-playbook/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/cnfeat/top-pm-skills/renewal-playbook"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/renewal-playbook.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.00070 | $0.02335 |
| Opus 5 | $0.00035 | $0.01167 |
| Sonnet 5 | $0.00014 | $0.00467 |
| Haiku 4.5 | $0.00007 | $0.00233 |
Grade A, and why
renewal-playbook 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 8d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renewal Playbook Skill
This skill produces a complete renewal playbook for a specific customer account, covering health assessment, commercial strategy, negotiation preparation, expansion opportunity mapping, and a step-by-step timeline. Output is ready for the CSM or account team to execute 90–180 days before renewal.
Required Inputs
Ask the user for these if not provided:
- Account name
- Renewal date
- Current ARR and proposed renewal ARR (if different)
- Account health — RAG status and main reasons (or describe the account situation)
- Key stakeholders — economic buyer, champion, and any detractors
- Renewal risk factors — budget pressure, low adoption, competitive threat, champion departure, etc.
- Expansion opportunity — any upsell or cross-sell potential?
- Contract terms — current plan, duration, and any terms up for renegotiation
Output Structure
Renewal Playbook: [Account Name]
Renewal date: [Date] Current ARR: [£/$/€ X] Target renewal ARR: [£/$/€ X — flat / +X% expansion / contraction risk] Health status: [Green / Amber / Red] CSM: [Name] Account executive: [Name] Days to renewal: [X days]
1. Account Health Snapshot
| Dimension | Score (1–5) | Evidence |
|---|---|---|
| Product adoption | [X/5] | [e.g. 3 of 5 purchased seats active; core feature used weekly] |
| Business outcomes | [X/5] | [e.g. Customer reports X% improvement in [metric]; no formal ROI review done] |
| Relationship depth | [X/5] | [e.g. Strong champion in [name/role]; limited exec sponsorship] |
| Support & satisfaction | [X/5] | [e.g. 2 open P2 tickets; last NPS 7; no escalations in 6 months] |
| Commercial engagement | [X/5] | [e.g. Invoice paid on time; no discount pressure raised yet] |
| Overall health | [X/5 — weighted] | [Green / Amber / Red] |
Renewal thesis: [One sentence: why this account will renew — or what must change for it to renew.]
2. Stakeholder Map
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.
- 8d ago First seen · 199 lines · 70 tokens per session scan A 60161f33ed2f
renewal-playbook is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 2,335 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.