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 bjorn-ingmanson/thefroject-plugins --skill renewal-orchestrationgit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-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/skills/bjorn-ingmanson/thefroject-plugins/renewal-orchestration)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/renewal-orchestration"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/renewal-orchestration/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/bjorn-ingmanson/thefroject-plugins/renewal-orchestration"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/renewal-orchestration.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.00080 | $0.01196 |
| Opus 5 | $0.00040 | $0.00598 |
| Sonnet 5 | $0.00016 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
renewal-orchestration 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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renewal Orchestration
Design a renewal program that gets activated 90 days before each customer's contract date and runs through contract execution. Single-deal tactical work (e.g., negotiate one specific renewal) belongs in renewal-strategist — this skill is the program design.
Gather context
Ask if not provided:
- Customer segments — segments by ARR or tier (SMB, mid-market, enterprise) often need different cadences.
- Renewal type — auto-renew with opt-out, opt-in, or active negotiation. Different economics.
- Contract length — annual, multi-year, monthly. Annual is the default this skill covers.
- Owner — CSM-driven, dedicated renewals manager, AM, or hybrid.
- Tooling — CRM with renewal-date triggers? Automation?
- Current state — last 12 months: gross retention, net retention, churn reasons.
The 90/60/30/0 cadence
For an annual contract with renewal date D:
Day -90 (start of renewal cycle)
- Owner: CSM.
- Action: review the account's value-realization scorecard. Run any value-realization-scorer or health-score-builder workflows.
- Decision: green/yellow/red track.
- Internal: brief renewal manager + AM if applicable.
- Customer-facing: optional check-in if any signal is yellow.
Day -60 (value review)
- Owner: CSM (with AM if expansion possible).
- Action: structured value-realization meeting with the customer's primary contact.
- Agenda: review intended outcomes from deal-close, status against each, plans for next year.
- Output: agreed renewal scope (same, expand, contract).
- If red track: escalate. Bring in exec sponsor or product input.
Day -45 (contract terms)
- Owner: AM or renewals manager.
- Action: send the formal renewal proposal.
- Include: proof of value (specific outcomes), pricing for next term, optional expansion, multi-year discount if applicable.
- Customer-facing: meeting to walk through the proposal, not email-only.
Day -30 (executive engagement, enterprise tier only)
- Owner: exec sponsor on your side.
- Action: outreach to customer's exec sponsor or champion+1.
- Goal: confirm continued strategic alignment, surface any blockers.
- Skip for SMB.
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.
- 11d ago First seen · 107 lines · 80 tokens per session scan A f05fe9f03e87
renewal-orchestration is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,196 once invoked, about $0.0004 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-31.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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.