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 redhat-developer/rhdh-skills --skill rhdh-jira-sprint-plangit clone --depth 1 https://github.com/redhat-developer/rhdh-skillsWrote 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/redhat-developer/rhdh-skills/rhdh-jira-sprint-plan)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-sprint-plan"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-sprint-plan/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/redhat-developer/rhdh-skills/rhdh-jira-sprint-plan"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-jira-sprint-plan.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.00171 | $0.00516 |
| Opus 5 | $0.00086 | $0.00258 |
| Sonnet 5 | $0.00034 | $0.00103 |
| Haiku 4.5 | $0.00017 | $0.00052 |
Grade A, and why
rhdh-jira-sprint-plan 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 11d 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.
What it actually says
Plan an RHDH sprint
Produce the numbers a planning call needs, before the call. Read-only until the team decides something.
Route
Load workflows/plan-sprint.md. Run it before each bi-weekly sprint planning
call.
Boundary with the neighbouring skills
- The review of the sprint that just ended — committed versus completed,
per-member results, demo checklist — is
/rhdh-jira-sprint-report. This skill looks forward; that one looks back. - Making the backlog worth planning from is
/rhdh-jira-refine. - Picking and setting an assignee is
/rhdh-jira-update. This skill invokes it for fill suggestions rather than scoring assignees itself. - Board IDs, sprint naming, JQL, and the Team field's JQL limitation are
/rhdh-jira-api. - Release-level readiness is
/rhdh-release-status.
Completion
Complete when velocity names the three sprints it averaged, carryover names every issue counted, and available capacity shows the subtraction that produced it. Report the JQL behind each number and whether any search was truncated. Say when story-point coverage is too thin to trust a velocity figure rather than publishing a number that looks solid. Fill suggestions are presented as suggestions — team members self-select during planning, and nothing here assigns anyone without approval.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 47 lines · 171 tokens per session scan A 2603a452782c
rhdh-jira-sprint-plan is a skill published in the GitHub repository redhat-developer/rhdh-skills (17 stars, last pushed 2d ago), licensed Apache-2.0. It adds 171 tokens to every session and 516 once invoked, about $0.0009 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.