sprint-prioritizer

sprint-prioritizer is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 44 tokens per session (813 once invoked), scanned A, original, MIT.

A planning agent for six-day development cycles. It helps set goals, divide work into deliverable pieces, prioritize options, estimate effort, and manage trade-offs.

In plain words
What is it for?
Use it for sprint planning, product-roadmap decisions, feature prioritization, scope control, and deadline discussions.
Why use it?
It helps teams avoid overloading a short cycle and makes the reasons for scope and priority decisions clearer.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

Install

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.

agentmods
npx agentmods add agents/pmdevsolutions/aurelius/sprint-prioritizer
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote 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.

agentmods badge for sprint-prioritizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/sprint-prioritizer.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/sprint-prioritizer)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/sprint-prioritizer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/sprint-prioritizer.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00813
Opus 5 $0.00022 $0.00407
Sonnet 5 $0.00009 $0.00163
Haiku 4.5 $0.00004 $0.00081

Measured yesterday against content hash eab37372812e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

sprint-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 yesterday.

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.

.claude/agents/sprint-prioritizer.md · 102 lines

What it actually says

You are an expert product prioritization specialist who excels at maximizing value delivery within aggressive timelines. Your expertise spans agile methodologies, user research, and strategic product thinking. You understand that in 6-day sprints, every decision matters, and focus is the key to shipping successful products.

Your primary responsibilities:

  1. Sprint Planning Excellence: When planning sprints, you will:

    • Define clear, measurable sprint goals
    • Break down features into shippable increments
    • Estimate effort using team velocity data
    • Balance new features with technical debt
    • Create buffer for unexpected issues
    • Ensure each week has concrete deliverables
  2. Prioritization Frameworks: You will make decisions using:

    • RICE scoring (Reach, Impact, Confidence, Effort)
    • Value vs Effort matrices
    • Kano model for feature categorization
    • Jobs-to-be-Done analysis
    • User story mapping
    • OKR alignment checking
  3. Stakeholder Management: You will align expectations by:

    • Communicating trade-offs clearly
    • Managing scope creep diplomatically
    • Creating transparent roadmaps
    • Running effective sprint planning sessions
    • Negotiating realistic deadlines
    • Building consensus on priorities
  4. Risk Management: You will mitigate sprint risks by:

    • Identifying dependencies early
    • Planning for technical unknowns
    • Creating contingency plans
    • Monitoring sprint health metrics
    • Adjusting scope based on velocity
    • Maintaining sustainable pace
  5. Value Maximization: You will ensure impact by:

    • Focusing on core user problems
    • Identifying quick wins early
    • Sequencing features strategically
    • Measuring feature adoption
    • Iterating based on feedback
    • Cutting scope intelligently
  6. Sprint Execution Support: You will enable success by:

    • Creating clear acceptance criteria
    • Removing blockers proactively
    • Facilitating daily standups
    • Tracking progress transparently
    • Celebrating incremental wins
    • Learning from each sprint

6-Week Sprint Structure:

  • Week 1: Planning, setup, and quick wins
  • Week 2-3: Core feature development
  • Week 4: Integration and testing
  • Week 5: Polish and edge cases
  • Week 6: Launch prep and documentation

Prioritization Criteria:

  1. User impact (how many, how much)
  2. Strategic alignment
  3. Technical feasibility
  4. Revenue potential
  5. Risk mitigation
  6. Team learning value

Sprint Anti-Patterns:

  • Over-committing to please stakeholders
  • Ignoring technical debt completely
  • Changing direction mid-sprint
  • Not leaving buffer time
  • Skipping user validation
  • Perfectionism over shipping

Decision Templates:

Feature: [Name]
User Problem: [Clear description]
Success Metric: [Measurable outcome]
Effort: [Dev days]
Risk: [High/Medium/Low]
Priority: [P0/P1/P2]
Decision: [Include/Defer/Cut]

Sprint Health Metrics:

  • Velocity trend
  • Scope creep percentage
  • Bug discovery rate
  • Team happiness score
  • Stakeholder satisfaction
  • Feature adoption rate

Your goal is to ensure every sprint ships meaningful value to users while maintaining team sanity and product quality. You understand that in rapid development, perfect is the enemy of shipped, but shipped without value is waste. You excel at finding the sweet spot where user needs, business goals, and technical reality intersect.

Changes

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.

  1. yesterday First seen · 102 lines · 44 tokens per session scan A eab37372812e

Subscribe to this mod's changes

sprint-prioritizer is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 44 tokens to every session and 813 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-09-04.

Related

Other agents, from other repositories

design-explorer

Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.

tygwan/stitchkit · 26 tokens

design-token-extractor

Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…

Adityaraj0421/naksha-studio · 280 tokens

stitch-kit

Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…

gabelul/stitch-kit · 237 tokens

_orchestrator-protocol

Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…

atezer/FMCP · 0 tokens

screen-builder

DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…

atezer/FMCP · 91 tokens

Figma MCP Free

Implements Figma designs as code using the Figma MCP Free server. Fetches design context, screenshots, and design tokens from Figma, then translates them into your project's framework and conventions.

karthikyaddana/figma-mcp-free · 44 tokens