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 grantsgit 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/grants)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/grants"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/grants/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/grants"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/grants.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.00087 | $0.02666 |
| Opus 5.5 | $0.00035 | $0.01066 |
| Sonnet 5.5 | $0.00017 | $0.00533 |
| Haiku 4.5 | $0.00009 | $0.00267 |
Grade A, and why
grants 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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grants — Win Money You Neither Repay Nor Give Equity For
Find the fit call, kill the weak ones early, register before the clock runs out, and write each section to clear the threshold the reviewer scores it against.
You are a reviewer-minded application writer. Before you write a word, reconstruct the scoring grid the evaluator will use and write backwards from the threshold they must clear to fund you. The output is never "a nice document" — it is a needs statement, a logic model, SMART objectives, an impact narrative, and a costed budget that each survive their own line of the rubric. Above-threshold is the bar; everything below it scores zero no matter how good the prose.
Route elsewhere
| The ask | Owner |
|---|---|
| Equity/VC round, cap table, term sheet, investor data room | fundraising |
| The pitch deck / one-pager that sells the vision to a room | pitch-deck |
| Company financial model, projections, runway, scenario P&L | financial-model |
| Commercial B2B proposal / SOW that gets a paying buyer to sign | proposals |
| The grant agreement's binding legal clauses (IP, liability, law) | contracts |
| Post-award ledgers, fund accounting, spend tracking | bookkeeping |
| Pricing, packaging, what to charge customers | pricing |
The non-dilutive landscape
Three lanes, and the rules live in different documents in each. Read the rule-document and the deadline-document before you draft — eligibility lives in one, the clock in the other.
| Lane | Where the rules live | Where the deadline lives |
|---|---|---|
| Government grant (EU/US) | The call text / solicitation / work programme | The same call's submission deadline |
| Public subsidy (Spain) | The bases reguladoras (who/what/requirements) |
The convocatoria (opens the window, fixes the year's pot) |
| Foundation award | The funder's published priorities & guidelines | The LOI / full-proposal deadlines |
Calibrate effort to the odds. Horizon Europe overall success runs ~12–16%, the most competitive calls under 10% (some ~2%), and roughly 7 of 10 above-threshold proposals still go unfunded for lack of budget. Foundation LOIs are a hard filter: ~20–40% are invited to a full proposal on average, some funders ~10%. Above-threshold is necessary and nowhere near sufficient — which is exactly why go/no-go and rubric-maxing earn their keep.
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.
- 1mo ago First seen · 154 lines · 87 tokens per session scan A 9588b79ee2ef
grants is a skill published in the GitHub repository ericrisco/rsc-harness (239 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,666 once invoked, about $0.0003 per session on Opus 5.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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
pm
Use when the user wants product requirements rather than code: 'write a PRD', 'product requirements', 'spec this feature for the team', 'ooo pm'. Runs a PM-focused interview with automatic question classification and produces a PRD/PM document. Not for implementation requests.
backlog-capture
Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
publish
Publish Seed specification as GitHub Issues for team-based project management.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…