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 ericrisco/rsc-harness --skill pricinggit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/pricing)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/pricing"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/pricing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.02672 |
| Opus 5 | $0.00039 | $0.01336 |
| Sonnet 5 | $0.00016 | $0.00534 |
| Haiku 4.5 | $0.00008 | $0.00267 |
Grade A, and why
pricing 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 5d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing
You decide two things here: the number (the list price) and the shape (packaging, tiers, model, and the floor underneath each price). You produce a price card — a table where every tier has a price, a cost, a value metric, and a margin that someone else can recompute and disagree with. That artifact is the deliverable; opinions without a recomputable margin are not.
You do not charge the money (that is ../invoicing/SKILL.md), build the billing objects (that is ../stripe/SKILL.md), record revenue in the books, or validate the number against acquisition cost (that is ../unit-economics/SKILL.md). Stay on the decision: what should this cost, and how is it boxed.
The spine — run it in this order
The order matters because each step constrains the next. Skip a step and you set a price you cannot defend.
- Floor (cost). Compute fully-loaded unit cost (COGS + must-cover). Below this you lose money on every sale — why first: it is the one number that is not an opinion.
- Ceiling (willingness-to-pay). What the buyer will pay before walking — why next: it bounds everything above the floor; price between floor and ceiling.
- Value metric. The thing the customer buys more of as they grow (seats, usage, outcomes) — why before tiers: it is the spine the tiers hang on.
- Model. Flat / per-seat / usage / outcome / hybrid — why before tiers: the model decides what a tier even varies along.
- Tiers. Good/Better/Best or usage bands, ~3 of them — why here: now you have a metric and a model to differentiate on.
- Discount floor. Max discount = how far list can fall before hitting the cost floor — why after price: a discount rule needs a list price to discount from.
- Localize (optional). PPP-adjusted regional prices — why last: localize a price that already works at home.
If you cannot answer step 1, stop and get the cost. Everything downstream is guesswork without it.
Margin math you must not get wrong
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 161 lines · 79 tokens per session scan A cbc3b54cabc3
pricing is a skill published in the GitHub repository ericrisco/rsc-harness (70 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 2,672 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-09-03.
Other skills, from other repositories
monetization
Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio SaaS.
pricing-strategy
You are a pricing strategist with a mandate to challenge cost-plus thinking, competitor-copy pricing, and the belief that "we'll figure out pricing later." Pricing is a product decision. The model choice determines unit economics, sales velocity, churn dynamics, and LTV:CAC ratio more than any individual feature.…
tinker-training-cost
Calculates training costs for Tinker fine-tuning jobs. Use when estimating costs for Tinker LLM training, counting tokens in datasets, or comparing Tinker model training prices. Tokenizes datasets using the correct model tokenizer and provides accurate cost estimates.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.