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.
git clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/feature-prioritizer)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/feature-prioritizer"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/feature-prioritizer.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.1 | $0.00028 | $0.00993 |
| Opus 5 | $0.00014 | $0.00496 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
feature-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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feature-prioritizer - Feature Priority Calculator
Triggers
- When deciding what to build next from a backlog
- When stakeholders disagree on priorities
- When resources are limited and trade-offs are needed
Usage
/feature-prioritizer [feature list or file path]
/feature-prioritizer --framework rice # Use RICE scoring
/feature-prioritizer --framework ice # Use ICE scoring
/feature-prioritizer --framework moscow # Use MoSCoW classification
Behavioral Flow
Phase 1: Input Collection
Accept feature list as text or from file:
Features can be provided as:
- Inline text (one feature per line)
- Markdown file with feature descriptions
- Backlog file reference
Phase 2: Framework Selection
If not specified, recommend based on context:
| Framework | Best For | Input Needed |
|---|---|---|
| RICE | Data-driven teams, quantitative | Reach, Impact, Confidence, Effort |
| ICE | Quick prioritization, early stage | Impact, Confidence, Ease |
| MoSCoW | Scope definition, stakeholder alignment | Categorization |
| Weighted | Custom criteria, multi-stakeholder | Custom weights |
Phase 3: Scoring
RICE Scoring:
RICE Score = (Reach × Impact × Confidence) / Effort
- Reach: How many users affected per quarter (number)
- Impact: How much impact per user (0.25/0.5/1/2/3)
- Confidence: How sure are we (100%/80%/50%)
- Effort: Person-months of work (number)
ICE Scoring:
ICE Score = Impact × Confidence × Ease (each 1-10)
Phase 4: Output
# Feature Prioritization — [Framework]
**Date**: YYYY-MM-DD
## Ranked Features
| Rank | Feature | Score | R | I | C | E | Recommendation |
|------|---------|-------|---|---|---|---|----------------|
| 1 | [Feature] | [N] | [N] | [N] | [N] | [N] | 🟢 Build Now |
| 2 | [Feature] | [N] | [N] | [N] | [N] | [N] | 🟢 Build Now |
| 3 | [Feature] | [N] | [N] | [N] | [N] | [N] | 🟡 Build Next |
| 4 | [Feature] | [N] | [N] | [N] | [N] | [N] | 🔴 Defer |
## Priority Tiers
### 🟢 Build Now (This Sprint/Month)
1. [Feature] — Score: [N] — [1-line why]
### 🟡 Build Next (Next Sprint/Month)
2. [Feature] — Score: [N] — [1-line why]
### 🔴 Defer (Backlog)
3. [Feature] — Score: [N] — [1-line why]
## Key Insights
- Highest ROI: [Feature] (high impact, low effort)
- Quick Win: [Feature] (moderate impact, very low effort)
- Big Bet: [Feature] (high impact, high effort)
- Reconsider: [Feature] (low impact, high effort)
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.
- 7d ago First seen · 127 lines · 28 tokens per session scan A 0b84ba4d1b0b
feature-prioritizer is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 993 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-31.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
fix
Universal debugging and fix application with semantic code analysis.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design
A command that turns an existing plan into a detailed technical design for building the feature.