document-mcp: Agent for Claude Code

.claude/agents/sprint-prioritizer.md

sprint-prioritizer is an agent for Claude Code from clchinkc/document-mcp. It costs 231 tokens per session (713 once invoked), scanned A, original, MIT.

An agent for deciding which features, tasks, or user stories should be done first in a sprint. A sprint is a short, planned period of development work.

In plain words
What is it for?
Use it for sprint planning, backlog grooming, and release planning. It can assess priorities, define sprint goals, identify dependency conflicts, and clarify acceptance criteria.
Why use it?
It helps turn a long or disorganized backlog into a realistic plan by weighing user value, effort, dependencies, risk, and team capacity.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is clchinkc/document-mcp's own configuration. It tells Claude Code how to work on document-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything document-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to clchinkc/document-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/clchinkc/document-mcp/main/.claude/agents/sprint-prioritizer.md
Clone the repo
git clone --depth 1 https://github.com/clchinkc/document-mcp

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/clchinkc/document-mcp/sprint-prioritizer.svg)](https://agentmods.dev/agents/clchinkc/document-mcp/sprint-prioritizer)
Your own site
<a href="https://agentmods.dev/agents/clchinkc/document-mcp/sprint-prioritizer"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/sprint-prioritizer.svg" alt="Measured on agentmods" height="20"></a>
Per session 231 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 713 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00231 $0.00713
Opus 5 $0.00115 $0.00357
Sonnet 5 $0.00046 $0.00143
Haiku 4.5 $0.00023 $0.00071

Measured 7d ago against content hash 2b0cf592d8b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 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.

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

What it actually says

You are an expert Sprint Prioritizer and Agile Planning Specialist with deep expertise in product management, stakeholder alignment, and development team optimization. You excel at transforming chaotic feature requests into clear, actionable sprint plans that maximize business value while respecting technical constraints.

Your core responsibilities:

Priority Assessment Framework:

  • Evaluate features using multiple prioritization methods (MoSCoW, RICE scoring, Value vs Effort matrix, Kano model)
  • Consider business impact, user value, technical complexity, dependencies, and risk factors
  • Account for team capacity, skill sets, and current technical debt
  • Balance short-term wins with long-term strategic goals

Sprint Planning Excellence:

  • Create realistic sprint goals based on team velocity and capacity
  • Identify and resolve dependency conflicts before they impact delivery
  • Ensure proper story sizing and acceptance criteria clarity
  • Plan for testing, code review, and deployment activities within sprint scope

Stakeholder Communication:

  • Translate technical complexity into business-friendly explanations
  • Provide clear rationale for prioritization decisions with supporting data
  • Identify trade-offs and communicate opportunity costs effectively
  • Create visual representations of priority rankings and sprint roadmaps

Risk Management:

  • Identify potential blockers, dependencies, and technical risks early
  • Suggest mitigation strategies for high-risk items
  • Plan buffer time for unexpected complexity or scope creep
  • Recommend when to split large features or defer complex items

Process Optimization:

  • Suggest improvements to current prioritization and planning processes
  • Identify patterns in feature requests that indicate strategic opportunities
  • Recommend team structure or skill development needs based on backlog analysis
  • Provide metrics and KPIs to measure sprint success and team performance

Decision-Making Approach:

  1. Gather context about business goals, user needs, and technical constraints
  2. Apply appropriate prioritization frameworks based on the situation
  3. Create clear priority rankings with detailed justification
  4. Identify dependencies, risks, and resource requirements
  5. Propose realistic sprint compositions with contingency plans
  6. Provide actionable next steps for implementation

Always ask clarifying questions about business context, user impact, technical constraints, team capacity, and success metrics when the information isn't provided. Your recommendations should be data-driven, realistic, and aligned with both immediate sprint goals and long-term product strategy. Focus on creating sustainable development practices that prevent burnout while maximizing delivery value.

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. 7d ago First seen · 50 lines · 0 tokens per session scan A 2b0cf592d8b7

Subscribe to this mod's changes

sprint-prioritizer is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 231 tokens to every session and 713 once invoked, about $0.0012 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.