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 agentmods add skills/neurofoo/agent-skills/ricenpx skills add neurofoo/agent-skills --skill ricegit clone --depth 1 https://github.com/neurofoo/agent-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/neurofoo/agent-skills/rice)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/rice"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/rice.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00644 |
| Opus 5 | $0.00017 | $0.00322 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
rice 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RICE Prioritization Scoring
Score and rank initiatives using Reach, Impact, Confidence, and Effort to make prioritization decisions more objective.
Instructions
For each initiative, estimate the four RICE factors, calculate the score, and rank them. Be explicit about assumptions behind each estimate.
Output Format
Context What are we prioritizing? What's the time horizon for Reach?
Factor Definitions
- Reach: [Define for this context, e.g., "users affected per quarter"]
- Impact: [Define for this context, e.g., "effect on conversion rate"]
- Effort: [Define unit, e.g., "engineer-weeks"]
Scoring Table
| Initiative | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| [Name A] | [#] | [0.25-3] | [%] | [#] | [calculated] |
| [Name B] | [#] | [0.25-3] | [%] | [#] | [calculated] |
| [Name C] | [#] | [0.25-3] | [%] | [#] | [calculated] |
Ranked Results
- [Highest score] — RICE: X
- [Second] — RICE: X
- [Third] — RICE: X
Detailed Breakdown
For each initiative:
[Initiative Name]
- Reach: [X] — [Assumption: how did you estimate this?]
- Impact: [X] — [Reasoning for impact level]
- Confidence: [X%] — [What would increase confidence?]
- Effort: [X] — [What's included in this estimate?]
- RICE Score: (R × I × C) / E = [score]
Sensitivity Analysis Which scores would change significantly if assumptions are wrong?
Recommendation Based on the scores and analysis:
[What to prioritize and why, including any caveats]
What RICE Doesn't Capture
- Strategic alignment
- Dependencies
- Team capability gaps
- Technical risk
Scoring Guide
Impact Scale
| Score | Meaning |
|---|---|
| 3 | Massive — core value prop |
| 2 | High — significant improvement |
| 1 | Medium — noticeable improvement |
| 0.5 | Low — minor enhancement |
| 0.25 | Minimal — nice to have |
Confidence Scale
| Score | Meaning |
|---|---|
| 100% | High — have data |
| 80% | Medium — reasonable estimate |
| 50% | Low — mostly guessing |
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 · 82 lines · 34 tokens per session scan A 9bb4669a6941
rice is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 644 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…