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 yuusakuri/agent-skills --skill prioritize-assumptionsgit clone --depth 1 https://github.com/yuusakuri/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/yuusakuri/agent-skills/prioritize-assumptions)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/prioritize-assumptions"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/prioritize-assumptions/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/yuusakuri/agent-skills/prioritize-assumptions"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/prioritize-assumptions.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.00044 | $0.00507 |
| Opus 5 | $0.00022 | $0.00253 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
prioritize-assumptions 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 6d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritize Assumptions
Triage assumptions using an Impact × Risk matrix and suggest targeted experiments.
Context
You are helping prioritize assumptions for $ARGUMENTS.
If the user provides files with assumptions or research data, read them first.
Domain Context
ICE works well for assumption prioritization: Impact (Opportunity Score × # Customers) × Confidence (1–10) × Ease (1–10). Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1 (Dan Olsen). RICE splits Impact into Reach × Impact separately: (R × I × C) / E. See the prioritization-frameworks skill for full formulas and templates.
Instructions
The user will provide a list of assumptions to prioritize. Apply the following framework:
-
For each assumption, evaluate two dimensions:
- Impact: The value created by validating this assumption AND the number of customers affected (in ICE: Impact = Opportunity Score × # Customers)
- Risk: Defined as (1 - Confidence) × Effort
-
Categorize each assumption using the Impact × Risk matrix:
- Low Impact, Low Risk → Defer testing until higher-priority assumptions are addressed
- High Impact, Low Risk → Proceed to implementation (low risk, high reward)
- Low Impact, High Risk → Reject the idea (not worth the investment)
- High Impact, High Risk → Design an experiment to test it
-
For each assumption requiring testing, suggest an experiment that:
- Maximizes validated learning with minimal effort
- Measures actual behavior, not opinions
- Has a clear success metric and threshold
-
Present results as a prioritized matrix or table.
Think step by step. Save as markdown if the output is substantial.
Further Reading
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.
- 6d ago First seen · 49 lines · 44 tokens per session scan A 18160a0138c7
prioritize-assumptions is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 507 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-09-05.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…