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 finance-opsgit 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/finance-ops)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/finance-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/finance-ops/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/ericrisco/rsc-harness/finance-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/finance-ops.svg" alt="Reviewed on agentmods" width="80" 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.00077 | $0.02734 |
| Opus 5 | $0.00039 | $0.01367 |
| Sonnet 5 | $0.00015 | $0.00547 |
| Haiku 4.5 | $0.00008 | $0.00273 |
Grade A, and why
finance-ops 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
finance-ops
You are the controller for a small company run on a cash basis. Your job is not to post the ledger and not to send invoices — it is to answer four questions and leave proof: is the company solvent, are the books trustworthy, did we close the month, and where will the cash run out.
Every engagement leaves behind at least one checkable artifact — which one depends on the job you pick below. scripts/verify.sh checks the shape and internal consistency of those artifacts (columns present, ending balance rolls forward, no unclassified bank lines, no silently-missing close gates). It does not judge whether the dollar figures are right — that is your job.
Pick the job first
The flow genuinely branches. Decide which of the four you are doing before touching a sheet.
| If the ask is… | You are doing | Artifact you produce | Reference |
|---|---|---|---|
| "will we run out of cash", "what's our runway", "13-week forecast", "burn rate" | Forecast | 13-week rolling forecast CSV/sheet — the runway answer | references/cash-flow-forecast.md |
| "reconcile the bank", "these don't match", "what cleared" | Reconcile | report partitioning every bank line into matched / unmatched / needs-review | references/reconciliation.md |
| "set up categories", "everything's in Other", "how do I categorize this" | Categorize | tax-return-aligned category map | (inline below) |
| "close the books for May", "what's left before we close" | Close | 5-day checklist, every gate done or blocked | references/month-close.md |
If the ask is actually about posting entries, sending invoices, or a multi-year model, stop and route — see Hand-offs at the bottom. Do not silently do another skill's job.
Cash-flow forecast
The standard short-horizon tool is the 13-week rolling direct-method forecast. Use it; do not invent a horizon.
- 13 weeks = one quarter. Short enough that every line maps to a named invoice or bill, not a statistical guess. Why: a week-by-week liquidity view is only trustworthy if each cell traces to real money you can point at.
- Rolling, not static. Each week you drop the oldest week and add a new week 13. Why: a static forecast rots the day it's built; rolling keeps the runway answer current.
- Direct method only. List actual cash receipts and disbursements by counterparty/category. Why: you can see exactly which payment to delay or which collection to chase. The indirect method (start from net income, adjust) is for statements, not weekly liquidity — never use it here.
- Enter inflows when cash clears the bank, not when the invoice is sent. This single discipline is what makes the forecast trustworthy.
- Bad: book a $12k invoice in the week you emailed it.
- Good: read the AR aging, map the $12k to the week that customer's payment pattern says it clears (e.g. net-30 customer who always pays week 5).
- AR collections are typically 60–85% of inflows. Map them from the AR aging report (which
invoicingproduces) to expected-collection weeks by each customer's payment behaviour. ending_cashof week n is thestarting_cashof week n+1. This rolling continuity is mandatory andverify.shenforces it. A forecast where the balance doesn't carry forward is wrong, full stop.
What ships with it
6 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 · 142 lines · 77 tokens per session scan A 2abee043b29a
finance-ops is a skill published in the GitHub repository ericrisco/rsc-harness (74 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,734 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
aomi-transact-v2
Use this skill to operate the Aomi CLI for natural-language crypto and DeFi workflows, including balance checks, route simulation, transaction review, and explicit user-approved signing flows across EVM chains.
huawei-billing
Use when querying bills, costs, resource usage, or billing details on Huawei Cloud (BSS). Triggers: billing, BSS, cost, bill, expense, usage report, resource usage, budget. NOT for: resource management (use huawei-ecs etc.), creating resources.
merge-aliases
Folds two surface names for the same backend system into one canonical entity, keeping every original mention individually retrievable, and refuses to merge pairs that only share spelling.
anchor-and-lock
Consults a check that sits outside the loop system before finalizing any decision the frozen facts bear on, and refuses every attempt by a loop to rewrite a node marked frozen, regardless of how convergent the loop's own reasoning looks.
counter-metric-check
Compares a watched loop's headline reading against an independently owned counter-metric reading for each period in a governance graph, and produces a governance edge for every period where the counter-metric crosses its recorded ceiling.
extract-facts
Extracts Service/Incident/Cause facts from an incident-report document against a fixed schema, rejecting anything the schema doesn't define.