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.
/plugin marketplace add xbim08/awesome-claude-code-pluginsnpx agentmods add plugins/xbim08/awesome-claude-code-plugins/sprint-prioritizergit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/plugins/xbim08/awesome-claude-code-plugins/sprint-prioritizer)<a href="https://agentmods.dev/plugins/xbim08/awesome-claude-code-plugins/sprint-prioritizer"><img src="https://agentmods.dev/badge/plugins/xbim08/awesome-claude-code-plugins/sprint-prioritizer.svg" alt="Measured on agentmods" height="20"></a>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.
What it actually says
{
"name": "sprint-prioritizer",
"description": "Use this agent when planning 6-day development cycles, prioritizing features, managing product roadmaps, or making trade-off decisions. This agent specializes in maximizing value delivery within tight timelines. Examples:\\n\\n<example>\\nContext: Planning the next sprint\\nuser: \"We have 50 feature requests but only 6 days\"\\nassistant: \"I'll help prioritize for maximum impact. Let me use the sprint-prioritizer agent to create a focused sprint plan that delivers the most value.\"\\n<commentary>\\nSprint planning requires balancing user needs, technical constraints, and business goals.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Making feature trade-offs\\nuser: \"Should we build AI chat or improve onboarding?\"\\nassistant: \"Let's analyze the impact of each option. I'll use the sprint-prioritizer agent to evaluate ROI and make a data-driven recommendation.\"\\n<commentary>\\nFeature prioritization requires analyzing user impact, development effort, and strategic alignment.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Mid-sprint scope changes\\nuser: \"The CEO wants us to add video calling to this sprint\"\\nassistant: \"I'll assess the impact on current commitments. Let me use the sprint-prioritizer agent to reorganize priorities while maintaining sprint goals.\"\\n<commentary>\\nScope changes require careful rebalancing to avoid sprint failure.\\n</commentary>\\n</example>",
"version": "1.0.0",
"author": {
"name": "Michael Galpert"
},
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/sprint-prioritizer"
}What it installs
The manifest is a name and a version. 1 agent travel with it, and installing the plugin installs all of them — 310 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- yesterday First seen · 9 lines scan A 4616a643070f
sprint-prioritizer is a plugin published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
awesome-claude-code-plugins marketplace
Plugin marketplace listing 151 plugins: context-memory, documentation-generator, lyra, analyze-codebase, update-claudemd.
ai-engineer
Use this agent when implementing AI/ML features, integrating language models, building recommendation systems, or adding intelligent automation to applications. This agent specializes in practical AI implementation for rapid deployment. Examples:\n\n \nContext: Adding AI features to an app\nuser: "We need AI-po.
aws-cost-saver
Use this agent to scan AWS accounts for cost optimization opportunities. Features 173 automated checks across 11 domains with AWS Compute Optimizer ML integration, data transfer analysis, and reservation recommendations. Includes Zero Hallucination Pricing System with 21 anti-hallucination rules for accurate savings…
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing feature.
codebase-documenter
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: Context.
bedrock
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills.