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/odinmb/ops-workflow/prioritizenpx skills add OdinMB/ops-workflow --skill prioritizegit clone --depth 1 https://github.com/OdinMB/ops-workflowWrote 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/odinmb/ops-workflow/prioritize)<a href="https://agentmods.dev/skills/odinmb/ops-workflow/prioritize"><img src="https://agentmods.dev/badge/skills/odinmb/ops-workflow/prioritize.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.00029 | $0.01014 |
| Opus 5 | $0.00015 | $0.00507 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
prioritize 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 3d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops Prioritize
Given a project's active plans, backlog, and goals, select 2-3 tasks for immediate autonomous execution. The output is a ranked shortlist with execution order — this skill does NOT execute them.
Context Required
You need the full project overview loaded (MEMORY.md, state, backlog, active plans) plus any newly identified work items from find-tasks.
Selection Criteria
Score each candidate task on these dimensions:
Impact (weight: high)
How much does completing this task move the project toward its goals?
- High: directly advances a primary goal, unblocks other work, or fills a critical knowledge gap
- Medium: advances a secondary goal, improves project quality, or creates useful reference material
- Low: nice-to-have, minor cleanup, or distant from current priorities
Feasibility (weight: high)
Can an autonomous agent complete this task without human input or real-world actions?
- High: pure research, writing, analysis, or knowledge management — all inputs are available
- Medium: mostly feasible, but may need assumptions about preferences or priorities
- Low: requires external information the agent can't access, real-world actions, or significant subjective judgment
Tasks with low feasibility should be skipped — they'll end up in the follow-up file anyway.
Independence (weight: critical)
Can this task be completed without depending on or conflicting with other selected tasks?
- Tasks that modify the same files are NOT independent
- Tasks where one's output is the other's input are NOT independent
- Tasks touching different backlog areas, state files, or reference topics are usually independent
Independence is a hard constraint, not a gradient. If two high-impact tasks conflict, pick the higher-impact one and find an independent alternative for the second slot.
Effort (weight: moderate)
Prefer a mix of effort levels. A good batch might be:
- 1 medium task (the main contribution of this cycle)
- 1-2 light tasks (quick wins that keep momentum)
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.
- 3d ago First seen · 116 lines · 29 tokens per session scan A d561e7f5417c
prioritize is a skill published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 1,014 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
knowledge-gaps
This skill should be used when the user asks about 'knowledge gaps', 'tool coverage', 'undocumented dependencies', 'undocumented tools', 'concept gaps', 'installed plugins', 'plugin coverage', 'undocumented skills', 'globally installed plugins/skills', 'what is installed on this machine', 'stale/outdated/drifted…
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-full-auto
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
people-intel
This skill should be used when the user asks to 'research person', 'person intel', 'people intel', 'who is [person]', 'who created [project]', 'who maintains [package]', 'add person to knowledge graph', 'enrich person note', 'update person note', 'document [person]', 'create person note for [name]'. Researches a…
dev-cycle
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
factory-api
API conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router composition, pagination shape, multi-field search via Drizzle ilike + or(), mutation lifecycle hooks, conditional query enabling, stale-time defaults, error response shape and…