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.
npx skills add opendatahub-io/ai-helpers --skill jira-sprint-summarygit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/skills/opendatahub-io/ai-helpers/jira-sprint-summary)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/jira-sprint-summary"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-sprint-summary/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/skills/opendatahub-io/ai-helpers/jira-sprint-summary"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-sprint-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00650 |
| Opus 5 | $0.00014 | $0.00325 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
jira-sprint-summary 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
odh-ai-helpers:jira-sprint-summary
Synopsis
/jira:sprint-summary <sprint-name> [options]
Description
Generate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights. This command provides data-driven insights for sprint retrospectives, stakeholder reporting, and process improvement.
Parameters
sprint-name: The exact name or identifier of the sprint (required)[options]: Optional flags for customizing output (see Options section)
Prerequisites
- JIRA MCP server must be configured and accessible
- Appropriate JIRA permissions to access sprint and issue data
- Valid sprint name that exists in the configured JIRA instance
Implementation
Core Features
- Sprint Overview: Retrieve basic sprint information (dates, status, goals)
- Issue Analysis: Categorize and analyze all issues in the sprint by:
- Issue type (Story, Bug, Task, Epic, etc.)
- Status (To Do, In Progress, Done, etc.)
- Priority levels
- Assignee distribution
- Progress Metrics: Calculate completion rates, velocity, and burndown data
- Team Insights: Analyze workload distribution and individual contributions
- Quality Metrics: Identify blocked issues, overdue items, and technical debt
Error Handling
- Missing JIRA Configuration: If JIRA MCP server is not configured or not working, provide clear setup instructions and troubleshooting steps
- Missing Sprint Name: If no sprint name provided, prompt for required parameter with examples
- Invalid Sprint: If sprint doesn't exist, suggest similar sprint names or provide guidance on finding correct sprint identifiers
- Permission Issues: Log authentication and authorization errors, report the failure to the user, and provide actionable feedback
Output Format
Generate a structured markdown report including:
- Executive summary with key metrics
- Sprint overview (dates, goals, team members)
- Issue breakdown tables and charts
- Progress visualization (completion rates, velocity trends)
- Risk assessment (blocked items, potential delays)
- Recommendations for sprint improvement
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 · 67 lines · 28 tokens per session scan A 662374eb9dd4
jira-sprint-summary is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 5d ago), licensed Apache-2.0. It adds 28 tokens to every session and 650 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-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…