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 erphq/skills --skill contracts-renewalsgit clone --depth 1 https://github.com/erphq/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/erphq/skills/contracts-renewals)<a href="https://agentmods.dev/skills/erphq/skills/contracts-renewals"><img src="https://agentmods.dev/badge/skills/erphq/skills/contracts-renewals/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/erphq/skills/contracts-renewals"><img src="https://agentmods.dev/badge/skills/erphq/skills/contracts-renewals.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.02772 |
| Opus 5 | $0.00035 | $0.01386 |
| Sonnet 5 | $0.00014 | $0.00554 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
contracts-renewals 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contracts & Renewals — Under 100 People
What This Process Does
Contract + renewal management at this size is storing contracts where you can find them, tracking renewal dates that matter, and turning recurring customers into steady-state revenue. You have 20–500 active contracts in various states (active, expiring, expired, terminated). Most are 1-year SaaS subscriptions or services engagements. Contract storage is usually Google Drive/Dropbox/Box (with good naming convention) or a lightweight CLM (Ironclad, Juro, SpotDraft). Renewal ownership sits with the founder, head of sales, or head of CS.
The work: know what you've signed, never miss a renewal date, execute renewals proactively (not reactively), and manage expansion motions deliberately. The biggest small-org mistakes: losing track of auto-renewal clauses, letting customers opt-out without a conversation, missing expansion opportunities, and pricing changes that surprise customers late.
Start Here: ERP•AI Templates
ERP•AI's Contract Lifecycle & Renewals template centralizes contract storage with searchable metadata (customer, ACV, renewal date, key terms), surfaces upcoming renewals on a calendar, automates renewal quote generation 90/60/30 days out, and drives renewal playbooks (proactive outreach, price uplift communication, expansion conversation). Pair with MSA Library for the standard paper and Renewal Playbooks for segment-specific approaches.
Build — Setting It Up
With Agents
- Contract repository: Agent ingests every signed contract (from DocuSign/PandaDoc), extracts key terms (ACV, start date, end date, renewal terms, notice period, pricing, auto-renewal), and catalogs in searchable metadata.
- Renewal calendar: Agent surfaces contracts renewing in next 120/90/60/30 days. Ownership assigned per account. Playbook triggered automatically.
- Renewal quote generation: 90 days before renewal, agent generates renewal quote with standard pricing uplift (or contract-specified rate). Routes to owner for review + send.
- Auto-renewal notice management: For auto-renewing contracts, agent ensures customer notices are sent per contract terms. For manual-renewal contracts, agent drives proactive outreach.
- Pricing-uplift tracking: Annual renewal with 5–10% uplift is standard. Agent tracks uplift acceptance rate + customer churn correlation.
- Expansion opportunity identification: Agent surfaces expansion signals — product usage growth, new team onboarded, CS conversation notes about pain points matching upsell products. Routes to CSM/AE.
- Churn-risk monitoring: Agent flags renewal risks — product engagement dropping, support ticket volume, stakeholder turnover, competitive evaluation signals. Triggers save-the-account playbook.
- Contract-search + summary: Ask agent "what does our contract with ACME say about data rights?" — pulls the clause with context.
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 · 138 lines · 70 tokens per session scan A 19b5e19c9786
contracts-renewals is a skill published in the GitHub repository erphq/skills (2 stars, last pushed 20d ago), licensed MIT. It adds 70 tokens to every session and 2,772 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-08-31.
Other skills, from other repositories
extendr-bindings
extendr conventions for exposing a Rust core to R: extendr macros and module registration, Robj type mapping, NA handling, rextendr builds, R package scaffolding, and CRAN compliance. Load when generating or reviewing extendr R bindings for a Rust library.
r-conventions
R code conventions covering R 4.1+, tidyverse/base style, styler/lintr, roxygen2, testthat, error handling, input validation, C/C++/Rust interop, and CRAN compliance. Load when writing or reviewing R code.
sec-plain-english
Draft, rewrite, or audit investor-facing financial and legal disclosure using an independently expressed interpretation of official SEC plain-English guidance. Use for prospectus summaries, risk factors, shareholder letters, offering materials, and securities disclosures that must be easier to understand without…
policy-drift-audit
Run the policy/process drift audit. Surfaces stale, superseded, duplicate, non-canonical, and conflicting policy documents using DocGraph's built-in drift engine. Presents findings and optional remediation suggestions without writing governance decisions.
full-after-care
Tiefe Pflegerunde für ein veröffentlichtes GitHub-Repository (Stufe 2): enthält den vollständigen surface-after-care-Durchlauf und ergänzt ihn um drei teure Schritte — rechtliche Ersteinschätzung über die Law-Checker mit Wiedervorlage nach einem Jahr (Gutachten bleibt gitignored im Repo), Querverweise zu verwandten…
lebende-verfassung
Neutrale moralisch-rechtliche Prüfinstanz für Politik und Entscheidungen — der lauffähige Prototyp des Forschungsprojekts "Die Position der Ungeborenen" (Schattenmodus Stufe 1). Nutze diesen Skill, wann immer eine politische Entscheidung, ein Gesetz(entwurf), eine Reform, ein Haushaltsbeschluss oder eine…