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 iteration-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/iteration-prioritization)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/iteration-prioritization"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/iteration-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/iteration-prioritization"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/iteration-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.00027 | $0.00824 |
| Opus 5 | $0.00014 | $0.00412 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
iteration-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iteration Prioritization
Overview
After launch, the question shifts from "should we build this?" to "what should we improve first?" This skill helps you balance user feedback, business goals, and technical debt when prioritizing post-launch iterations.
When to Use
- A feature has shipped and you have initial data
- You're planning the next iteration cycle
- You have a backlog of improvements from user feedback
- You need to decide between new features and polish
- Don't use for: pre-launch prioritization (use hypothesis-prioritization), strategic planning (use quarterly-planning workflow)
Instructions
1. Gather Input Signals
Before prioritizing, collect:
- Usage data: What are people using? What are they ignoring?
- Feedback: What are users asking for? What's confusing them?
- Support tickets: What issues are generating the most volume?
- Metrics: Did your success metrics improve? Which ones missed?
- Technical debt: What's slowing the team down?
2. Categorize Work Types
Not all work is the same. Balance across:
- Value additions: New capabilities based on user needs
- Quality improvements: Performance, reliability, polish
- Debt reduction: Clean up, refactor, improve developer experience
- Metrics-driven: Improvements to move specific metrics
3. Apply a Balanced Framework
Effort/Impact with a twist — for each candidate, score:
| Category | Weight | Questions |
|---|---|---|
| User impact | High | How many users benefit? How much? |
| Business impact | Medium | Does this drive retention, conversion, or revenue? |
| Metric alignment | High | Does this move our North Star or key metrics? |
| Strategic fit | Medium | Does this align with product strategy? |
| Urgency | Low | Is this a blocker or degradation? |
| Effort | - | How many days/weeks? |
4. Create the Iteration Backlog
Organize into:
- Now (this sprint): Quick wins, critical fixes, highest impact
- Next (next sprint): Solid improvements, lower urgency
- Later (backlog): Worth doing, lower priority
- Never: Explicit kill decisions (document why)
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 · 87 lines · 27 tokens per session scan A d4ae32005837
iteration-prioritization is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 824 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.