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 hajekim/agentic-design-patterns-skills --skill prioritizationgit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-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/hajekim/agentic-design-patterns-skills/prioritization)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-skills/prioritization"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/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/hajekim/agentic-design-patterns-skills/prioritization"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/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.00410 | $0.03858 |
| Opus 5 | $0.00205 | $0.01929 |
| Sonnet 5 | $0.00082 | $0.00772 |
| Haiku 4.5 | $0.00041 | $0.00386 |
Grade A, and why
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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prioritization — 100% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritization Pattern
Overview
The Prioritization Pattern equips agents with the ability to intelligently order and schedule their work — managing multiple competing tasks by continuously evaluating their relative importance, urgency, and expected impact. Rather than executing tasks in arbitrary order, prioritizing agents allocate their limited attention and resources to what matters most.
Core Principle: Not all tasks are equal — do the right things in the right order, not just things in the order they arrived.
When This Skill Applies
Activate this pattern when:
- Agents receive multiple concurrent requests that cannot all be handled immediately
- Some tasks are time-sensitive (deadlines, SLAs, real-time alerts) while others can wait
- Resources are limited and must be allocated to highest-value tasks first
- Different users or workloads have different priority levels
- Long-running tasks must be interruptible when higher-priority work arrives
- The agent must balance urgent-but-less-important vs. important-but-not-urgent tasks
Rule of thumb: If the agent has more to do than time to do it — it needs prioritization.
Priority Frameworks
Eisenhower Matrix (Urgency × Importance)
│ IMPORTANT │ NOT IMPORTANT │
────────────────┼─────────────┼───────────────┤
URGENT │ Do First │ Delegate/Auto │
────────────────┼─────────────┼───────────────┤
NOT URGENT │ Schedule │ Eliminate │
────────────────┴─────────────┴───────────────┘
Multi-Factor Priority Scoring
Priority = (Urgency × 0.4) + (Impact × 0.3) + (Effort × 0.2) + (Dependencies × 0.1)
WSJF (Weighted Shortest Job First)
WSJF = (Business Value + Time Criticality + Risk Reduction) / Job Size
Best for software/product backlogs — prioritizes small, high-value tasks.
DEFINE → PLAN → ACTION Workflow
DEFINE
Map prioritization requirements:
- What task types does the agent handle? (Categorize by domain)
- What dimensions determine priority? (Urgency, impact, effort, dependencies)
- What are the SLAs per task type? (Response time requirements)
- How dynamic is priority? (Static assignment vs. real-time re-evaluation)
- Can tasks be preempted? (Can high-priority work interrupt in-progress tasks?)
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.
- 9d ago First seen · 406 lines · 410 tokens per session scan A 67ce8b58b192
prioritization is a skill published in the GitHub repository hajekim/agentic-design-patterns-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 410 tokens to every session and 3,858 once invoked, about $0.0020 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
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
prompt-optimizer
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite…
openclaw-persona-forge
A persona-design guide for OpenClaw agents, including their identity, personality, boundaries, names, and avatar prompts. OpenClaw is the specific agent platform this guide targets.
gemini-api
Google Gemini API patterns for Python and TypeScript. Covers content generation, streaming, tool use (function calling), vision, system instructions, context caching, batch requests, and agent workflows. Use when building applications with the Gemini API or Google Generative AI SDKs.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.