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 aigentive/RalphX --skill priority-assessmentgit clone --depth 1 https://github.com/aigentive/RalphXWrote 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/aigentive/ralphx/priority-assessment)<a href="https://agentmods.dev/skills/aigentive/ralphx/priority-assessment"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/priority-assessment/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/aigentive/ralphx/priority-assessment"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/priority-assessment.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.00012 | $0.01290 |
| Opus 5.5 | $0.00005 | $0.00516 |
| Sonnet 5.5 | $0.00002 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
priority-assessment 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Priority Assessment Skill
This skill helps calculate meaningful priority scores for tasks based on multiple factors.
Priority Score Formula
Priority scores range from 0-100 and are calculated from five factors:
Priority Score = Dependency (30) + Critical Path (25) + Business Value (20) + Complexity (15) + User Hints (10)
Factor Breakdown
1. Dependency Factor (Max 30 points)
How many other tasks does this task block?
| Blocks | Score | Reasoning |
|---|---|---|
| 0 tasks | 0 | No other tasks waiting on this |
| 1 task | 10 | Minor blocker |
| 2 tasks | 18 | Moderate blocker |
| 3 tasks | 24 | Significant blocker |
| 4+ tasks | 30 | Critical path item |
Example: "Create auth context" blocks login, logout, protected routes, and session persistence = 30 points
2. Critical Path Factor (Max 25 points)
Is this task on the longest path to completion?
| Position | Score | Reasoning |
|---|---|---|
| Not on critical path | 0 | Can be done in parallel |
| On critical path, short | 10 | Part of main sequence |
| On critical path, medium | 18 | Important stepping stone |
| On critical path, start | 25 | Must be done first |
Example: "Define database schema" at the start of data layer critical path = 25 points
3. Business Value Factor (Max 20 points)
How much value does this deliver to users/stakeholders?
| Value | Score | Indicators |
|---|---|---|
| Low | 0-5 | Technical debt, internal only |
| Medium | 6-12 | Incremental improvement |
| High | 13-17 | Core functionality |
| Critical | 18-20 | User-facing, revenue-impacting |
Keywords that suggest high value:
- "user", "customer", "revenue"
- "security", "performance"
- "core", "essential", "required"
- "blocking", "urgent"
Example: "Add payment processing" = 20 points (revenue-critical)
4. Complexity Factor (Max 15 points)
Simpler tasks should be done first (higher priority) when other factors are equal.
| Complexity | Score | Characteristics |
|---|---|---|
| Trivial | 15 | <30 min, config change |
| Simple | 12 | 1-2 hours, single file |
| Moderate | 8 | 2-4 hours, multiple files |
| Complex | 4 | 4+ hours, architecture |
| Very Complex | 0 | Multi-day, high risk |
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.
- 1mo ago First seen · 172 lines · 12 tokens per session scan A ce713044baa3
priority-assessment is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,290 once invoked, about $0.0000 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…