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 uthumany/uthy-legacy-os --skill hypothesis-prioritizationgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/hypothesis-prioritization)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/hypothesis-prioritization"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/hypothesis-prioritization/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/uthumany/uthy-legacy-os/hypothesis-prioritization"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/hypothesis-prioritization.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.00035 | $0.01132 |
| Opus 5 | $0.00017 | $0.00566 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
hypothesis-prioritization 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 11d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hypothesis Prioritization
Overview
You can't build everything. Hypothesis prioritization helps you choose which ideas to pursue next using proven scoring frameworks. This skill covers RICE, ICE, Value-vs-Effort quadrants, and assumption-based prioritization — choose the right framework for your context.
When to Use
- Choosing which solution to build next
- Ranking experiment ideas with limited testing capacity
- Aligning stakeholders on priorities with a transparent framework
- Deciding between competing feature requests
- Don't use for: comparing fundamentally different products (apples to oranges), urgent bug fixes (just fix them), strategic bets (different framework needed)
Instructions
1. Define Your Candidates
List the solutions, features, or experiments to prioritize. Each needs:
- Name and one-line description
- The hypothesis you're testing
- Who it serves
2. Choose a Framework
RICE (best for product features):
- Reach: How many users will this impact in a given time period? (scale 1-10)
- Impact: How much impact per user? (scale: 0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive)
- Confidence: How confident are we in our estimates? (scale: 50%=low, 80%=medium, 100%=high)
- Effort: How many person-months? (estimate in person-months)
- Score: (Reach × Impact × Confidence) / Effort
ICE (best for experiments):
- Impact: How impactful will this be? (1-10)
- Confidence: How confident are we? (1-10)
- Ease: How easy is this to test? (1-10)
- Score: (Impact + Confidence + Ease) / 3
Value vs. Effort Quadrant (best for stakeholder alignment):
- Plot items on a 2x2 matrix: Value (Y) vs. Effort (X)
- Quick wins (high value, low effort) → do first
- Big bets (high value, high effort) → plan carefully
- Fill-ins (low value, low effort) → do when idle
- Avoid (low value, high effort) → don't do
3. Score Your Items
Be transparent about scoring. Document:
- Who assigned the scores
- What data informed each score
- ✅ means there's supporting evidence
- ⚠️ means it's an estimate (flag low-confidence items)
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.
- 11d ago First seen · 108 lines · 35 tokens per session scan A a8dc721c089d
hypothesis-prioritization is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,132 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-31.
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…