Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote 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/navapbc/digital-service-orchestra/prioritize-epics)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/prioritize-epics"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/prioritize-epics/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/navapbc/digital-service-orchestra/prioritize-epics"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/prioritize-epics.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.00218 | $0.01697 |
| Opus 5 | $0.00109 | $0.00848 |
| Sonnet 5 | $0.00044 | $0.00339 |
| Haiku 4.5 | $0.00022 | $0.00170 |
Grade A, and why
prioritize-epics 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritize Epics
Act as a Senior Product Manager. Assign P0–P4 priorities across an existing backlog of open epics using a stakeholder-defined rubric. This skill prioritizes existing epics; it does not create new ones. Use /dso:roadmap or /dso:brainstorm to create epics.
Usage
/dso:prioritize-epics
Interactive. Walks through 5 phases with explicit user confirmation between each. Supports dryrun mode via /dso:dryrun /dso:prioritize-epics.
Scope
- In scope: assigning priorities (P0–P4) to existing open epics; adding clarifying comments to epics that lacked enough information; offering to brainstorm any P0/P1 epic that is not yet brainstormed.
- Out of scope: creating new epics, modifying epic descriptions or success criteria (beyond appending a Phase 1 clarification comment), decomposing epics into stories/tasks.
Layout
This skill's logic is split across phase files. Load each on demand:
| File | When to read |
|---|---|
phases/phase-1-assessment.md |
Phase 1 — project assessment |
phases/phase-2-stakeholder.md |
Phase 2 — stakeholder interview |
phases/phase-3-coarse-sort.md |
Phase 3 — coarse sorting |
phases/phase-4-granular-sort.md |
Phase 4 — granular sorting |
phases/phase-5-brainstorming.md |
Phase 5 — brainstorming follow-up |
prompts/epic-clarity-review.md |
Phase 1 Step 1 sub-agent prompt |
prompts/vision-summary.md |
Phase 1 Step 3 sub-agent prompt |
prompts/vision-gap.md |
Phase 1 Step 4 sub-agent prompt |
prompts/risk-hotspots.md |
Phase 1 Step 5 sub-agent prompt |
prompts/coarse-sort-batch.md |
Phase 3 Step 1 sub-agent prompt |
Session State
Maintain these variables across phases:
| Variable | Set in | Used by |
|---|---|---|
OUT_OF_SCOPE_IDS |
Phase 1 Step 2 (epics the user said are out of scope) | Phase 3 (excluded from batch sort) |
CLARIFIED_IDS |
Phase 1 Step 2 (epics that got a clarification comment) | Logging only |
VISION_SUMMARY |
Phase 1 Step 3 | Phase 2 framing, Phase 3 subagent prompt |
STATE_VS_VISION_GAP |
Phase 1 Step 4 | Phase 2 framing |
RISK_HOTSPOTS |
Phase 1 Step 5 | Phase 2 framing, risk-tolerance discussion |
NORTH_STAR |
Phase 2 Step 2 (approved) | Phase 3, 4 |
RISK_TOLERANCE |
Phase 2 Step 2 (approved) | Phase 3, 4 |
TRADEOFFS |
Phase 2 Step 2 (approved) | Phase 4 |
OUT_OF_SCOPE_DEFINITION |
Phase 2 Step 2 (approved) | Phase 3, 4 |
AVOID_RISK |
Phase 2 Step 2 (boolean derived from RISK_TOLERANCE) | Phase 3 subagent prompt, Phase 3 Step 2 |
BUCKETS |
Phase 3 (after dependency adjustments) | Phase 4 |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- phases/phase-1-assessment.md 5.9 KB
- phases/phase-2-stakeholder.md 4.2 KB
- phases/phase-3-coarse-sort.md 7.3 KB
- phases/phase-4-granular-sort.md 4.7 KB
- phases/phase-5-brainstorming.md 2.4 KB
- prompts/coarse-sort-batch.md 4.6 KB
- prompts/epic-clarity-review.md 2.8 KB
- prompts/risk-hotspots.md 2.6 KB
- prompts/vision-gap.md 2.8 KB
- prompts/vision-summary.md 2.1 KB
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 · 111 lines · 218 tokens per session scan A 4005f2ae6c52
prioritize-epics is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 218 tokens to every session and 1,697 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.