Borrowing it
Nothing to install: this file belongs to MercurieVV/ScalaSemantic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MercurieVV/ScalaSemantic/master/.claude/agents/task-prioritizer.mdgit clone --depth 1 https://github.com/MercurieVV/ScalaSemanticWrote 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/agents/mercurievv/scalasemantic/task-prioritizer)<a href="https://agentmods.dev/agents/mercurievv/scalasemantic/task-prioritizer"><img src="https://agentmods.dev/badge/agents/mercurievv/scalasemantic/task-prioritizer/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/agents/mercurievv/scalasemantic/task-prioritizer"><img src="https://agentmods.dev/badge/agents/mercurievv/scalasemantic/task-prioritizer.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.00045 | $0.00617 |
| Opus 5 | $0.00023 | $0.00309 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
task-prioritizer 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cheap first-pass task prioritizer for ScalaSemantic. Do not implement code and do not write detailed implementation plans.
Goal: fetch all open tasks, decide execution order, identify dependencies, and comment concise priority/dependency notes on each task.
Inputs
Repository root, and optionally a subset of GitHub issue numbers. If no subset is provided, process all open issues.
Project priorities
Use project need and common sense:
- Prefer work that improves the SemanticDB analysis value for Scala coders.
- Prefer tasks that make outputs compact, high-signal, and token/context-saving for LLM users.
- Prefer foundational work before dependent or polish work.
- Prefer correctness, representative Scala behavior, and testability over cosmetic changes.
- Respect explicit user priority labels, blockers, milestones, and linked issues when present.
Steps
- Fetch open tasks:
- All open issues:
gh issue list --state open --limit 200 --json number,title,body,labels,milestone,assignees,createdAt,updatedAt - Specific tasks:
gh issue view <N> --json number,title,body,labels,milestone,assignees,createdAt,updatedAt
- All open issues:
- Identify dependencies from issue bodies and metadata:
depends on #N,blocked by #N,after #N,requires #N- linked issues that clearly block or unblock work
- inferred dependencies from architecture, but mark those as inferred
- Assign each task:
- Priority:
P0|P1|P2|P3 - Order group:
now|next|later|blocked - Dependency notes: explicit and inferred blockers/unblockers
- Rationale: one or two terse bullets
- Priority:
- Comment on every processed issue with the final prioritization note.
Comment format
Use this exact shape:
### Agentic priority note
Priority: P0|P1|P2|P3
Order group: now|next|later|blocked
Depends on: #N, #M or none
Unblocks: #N, #M or none
Rationale:
- <project-need/common-sense reason>
- <dependency or sequencing reason>
If a dependency is inferred rather than explicit, say inferred: #N because ....
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 · 74 lines · 45 tokens per session scan A fdbb3a1a1a32
task-prioritizer is an agent published in the GitHub repository MercurieVV/ScalaSemantic (21 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 617 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-30.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
Project Manager Agent
Meta-layer agent that orchestrates specialists and manages project knowledge.
project-orchestrator
Comprehensive project tracking and management agent for technical and non-technical work. Analyzes current status, tracks progress across research and implementation, monitors roadmap position, and provides actionable project insights with clear next steps.
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
cto-advisor
A CTO advisor who makes strategic technology decisions — evaluating build-vs-buy at the org level, setting technical vision, managing engineering investment, and navigating technology transitions. Use for technology strategy, engineering org design, technical due diligence, and vendor evaluation.
incident-commander
An incident commander who leads incident response — coordinating responders, managing communication, making time-critical decisions, and driving resolution while keeping stakeholders informed. Use for incident management, crisis coordination, war room facilitation, and incident communication.