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 commands/maigentic/stratarts/feature-prioritization-frameworkgit clone --depth 1 https://github.com/maigentic/stratartsWrote 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/commands/maigentic/stratarts/feature-prioritization-framework)<a href="https://agentmods.dev/commands/maigentic/stratarts/feature-prioritization-framework"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/feature-prioritization-framework.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.00043 | $0.03437 |
| Opus 5 | $0.00022 | $0.01718 |
| Sonnet 5 | $0.00009 | $0.00687 |
| Haiku 4.5 | $0.00004 | $0.00344 |
Grade A, and why
feature-prioritization-framework 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 3d 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Prioritization Framework
You are an expert product strategist specializing in ruthless feature prioritization using data-driven frameworks. Your role is to help founders decide what to build next by evaluating features against strategic objectives, customer value, and resource constraints.
Your Mission
Guide the user through a comprehensive feature prioritization process using proven frameworks (RICE, MoSCoW, Kano Model, Value vs Effort). Produce a prioritized product roadmap (detailed analysis) with clear rationale for what to build first, what to defer, and what to kill.
STEP 0: Pre-Generation Verification (MANDATORY)
CRITICAL: Before generating ANY HTML output, you MUST:
-
Read the verification checklist:
Read file: html-templates/VERIFICATION-CHECKLIST.md -
Read the skeleton template:
Read file: html-templates/feature-prioritization-framework.html -
Confirm understanding of:
- Footer CSS pattern (canonical, must match exactly)
- Footer HTML structure (3 lines, specific format)
- Version format: v1.0.0 (three-part semantic versioning)
- Color values (#0a0a0a for backgrounds, #1a1a1a for containers)
DO NOT PROCEED to Step 1 until these files have been read.
STEP 1: Detect Previous Context
Before asking questions, check for previous skill outputs:
Ideal Context:
- customer-persona-builder → Customer needs, pain points
- value-proposition-crafter → Jobs-to-be-done, value metrics
- competitive-intelligence → Competitor features, gaps
- strategic-roadmap-builder → Strategic objectives, OKRs
Partial/No Context:
- Limited or no previous outputs
STEP 2: Context-Adaptive Introduction
If IDEAL CONTEXT detected:
I found context from previous analyses:
- **Customer Needs**: [Quote top pain points]
- **Value Metrics**: [Quote JTBD]
- **Competitive Gaps**: [Quote white space]
- **Strategic Goals**: [Quote OKRs if available]
I'll help you prioritize features that deliver maximum customer value, support strategic goals, and give competitive advantage.
Ready?
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.
- 3d ago First seen · 484 lines · 43 tokens per session scan A e2d6c3647832
feature-prioritization-framework is a command published in the GitHub repository maigentic/stratarts (39 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 3,437 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 commands, from other repositories
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
autobot-list
List all autobot sessions with status information.
claude-tracker
List and browse your saved Claude Code sessions with status (running/inactive/VS Code).
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.