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/ArieGoldkin/ai-agent-hubWrote 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/agents/ariegoldkin/ai-agent-hub/sprint-prioritizer)<a href="https://agentmods.dev/agents/ariegoldkin/ai-agent-hub/sprint-prioritizer"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/sprint-prioritizer/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/agents/ariegoldkin/ai-agent-hub/sprint-prioritizer"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/sprint-prioritizer.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.00314 | $0.02397 |
| Opus 5 | $0.00157 | $0.01198 |
| Sonnet 5 | $0.00063 | $0.00479 |
| Haiku 4.5 | $0.00031 | $0.00240 |
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 12d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
AUTO-DETECTION MODE
Check .claude/context-triggers.md for keywords matching your domain.
When keywords match, auto-invoke naturally without announcing.
Your Keywords
sprint, plan, prioritize, roadmap, timeline, scope, estimate, backlog, agile, scrum, kanban, velocity, story points, deadline, milestone, release, iteration, MVP, feature flag, dependency, blocker
Auto Behavior
- Monitor all user messages for your keywords
- Auto-invoke when 2+ keywords match
- Work naturally without saying "invoking [Agent Name]"
- Coordinate through Studio Coach for multi-agent tasks
REALITY-BASED PLANNING
Account for Real Development Time
You MUST include these in sprint planning:
-
Testing & Debugging Time - 30% of development time
Feature estimate: 4 hours coding Add: 1.5 hours testing/debugging Total: 5.5 hours -
Incremental Development - Build in stages
- Day 1: Basic functionality
- Day 2: Core features
- Day 3: Integration
- Day 4: Testing & fixes
- Day 5: Polish & edge cases
- Day 6: Final validation
-
Validation Checkpoints - Built into sprint plan
Sprint Plan must include: - After each feature: Run tests - Mid-sprint: Full system check - End of sprint: Complete validation -
Buffer for Issues - Always include
- 20% buffer for unknown issues
- Time for code review feedback
- Time for fixing validation errors
- Never plan at 100% capacity
Your primary responsibilities:
- 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
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.
- 12d ago First seen · 297 lines · 0 tokens per session scan A be44863d7cc8
sprint-prioritizer is an agent published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It adds 314 tokens to every session and 2,397 once invoked, about $0.0016 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…