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/asysta-act/agent-flow/prioritizenpx skills add asysta-act/agent-flow --skill prioritizegit clone --depth 1 https://github.com/asysta-act/agent-flowWrote 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/asysta-act/agent-flow/prioritize)<a href="https://agentmods.dev/skills/asysta-act/agent-flow/prioritize"><img src="https://agentmods.dev/badge/skills/asysta-act/agent-flow/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.00014 | $0.00460 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 4d 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.
What it actually says
Prioritize
Input: $ARGUMENTS = optional --limit <N> (default: 20), --output <path> (default: stdout)
Configuration
Read Automation Config from CLAUDE.md section ## Automation Config:
- Issue Tracker: Type, Instance, Project, Bug query
- Optional: Feature Workflow → Feature query
- Optional: Metrics → for historical data
0. MCP pre-flight check
Before any pipeline operation, verify MCP tool availability:
- Read Type from Automation Config (Issue Tracker section)
- Check that at least one
mcp__*tool matching the tracker type is accessible - If not accessible → STOP with: "Cannot connect to your {Type} issue tracker. Is the {Type} integration configured? Run
/agent-flow:check-setupfor diagnostics."
Orchestration
1. Fetch issues
Via MCP server (per Issue Tracker → Type), fetch open issues (Bug query + Feature query). Limit = --limit flag.
2. Enrich with history
If a metrics report exists (./reports/metrics.md or Metrics → Output from config), read per-area failure patterns and success rates.
3. Run priority-engine
Before dispatch, check Agent Overrides: follow ../../core/agent-override-injector.md for priority-engine overrides.
You MUST invoke Task(subagent_type='agent-flow:priority-engine', model='opus'). DO NOT inline-execute.
Context: list of issues + historical data (if available).
If priority-engine fails or returns an error, display: "Prioritization failed: {reason}" and stop.
4. Output
Display the agent's result. If --output is specified → write to file.
Rules
- Read-only — no changes to the issue tracker
- If no issues found → "No open issues found matching the query"
- Data is read via MCP servers
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.
- 4d ago First seen · 53 lines · 14 tokens per session scan A 14417763e0ba
prioritize is a skill published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 460 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-30.
Other skills, from other repositories
summon
Autonomous orchestrator for manifest work items through the development lifecycle. Use when running egregore to process a backlog automatically.
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
log
Capture front door. Logs 1..N observations as card files at docs/work/{ID}.md (BUG / DEBT / GAP), gateway-inline — no dispatch. Use when the user says "log this", "track that", "note this down", or types /super-bootstrap:log — and when Claude needs to file its own findings (out-of-scope findings from a review, audit…
triage
Read-only grounding phase for a card — every card's pickup. /super-bootstrap:triage {ID} dispatches the triage subagent (Opus) to ground the card cold — premise verify, aim validate, blast collect — and append a Verdict block — ## Verdict — auto-fix · {date} (Fix-shape / Probe-deps / Execution tags) or ## Verdict …
drain
Parallel-worktree auto-drain of the board. One /super-bootstrap:drain turn = scan the pipeline sources (specs/plans/backlog, plus the scale module's test queue when present) → keep only admissible items → relation-analyze into a conflict-free wave → confirm with the user → spawn one isolated git worktree + headless…
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.