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-release-capacity-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-release-capacity-plan)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-release-capacity-plan"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-capacity-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-release-capacity-plan"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-capacity-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.00195 | $0.00804 |
| Opus 5.5 | $0.00078 | $0.00322 |
| Sonnet 5.5 | $0.00039 | $0.00161 |
| Haiku 4.5 | $0.00019 | $0.00080 |
Grade A, and why
rhdh-release-capacity-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 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan RHDH release capacity
Say whether a team can take the candidate Features for a named release, with both ledgers and the arithmetic that produced them. Read-only.
Route
Load workflows/plan-capacity.md. Run it when a team is choosing which
rhdh-X.Y-candidate Features to take for a release.
Boundary with the neighbouring skills
- Filling the next sprint — carryover, three-sprint velocity, ready queue —
is
/rhdh-jira-sprint-plan. This skill looks across remaining sprints to Code Freeze. - What is still open against the release, the PI funnel, and Feature readiness
are
/rhdh-release-status. That skill reports status; this one reports fit. - Milestone dates, including Code Freeze and Feature Freeze, are
/rhdh-release-schedule. - Team name to Cloud ID and board is
/rhdh-release-teams. - Board IDs, JQL, Team-field traps, roster GraphQL, and the Greenhopper
sprint-report seam are
/rhdh-jira-api. - What a T-shirt size means when writing an issue is
/rhdh-jira-authoring. This skill does not use that sprint-effort table for demand. Unsized T-shirts use a placeholder Fibonacci map in the script until a calibrated conversion exists. Never treat the Size field's 1–5 as story points.
Completion
Complete when both ledgers name the sample sprints, the remaining-sprint count
through Code Freeze (three-week slots unless the snapshot overrides
sprint_days), the meeting factor, and whether interrupt was retrieved; when
fillable planned capacity is shown separately from the interrupt reserve, and
required demand is fit against fillable rather than against mixed completed
work; when every candidate Feature is either estimated (Epic children, or a
T-shirt placeholder) or listed as unsized; when any T-shirt fallback ran, the
placeholder map is printed with the demand; and when stretch Features are
called out as first cuts. Report the JQL behind the sample and whether any
search was truncated. Say when story-point coverage is under 50% and the unit
switched to issue counts. Print the arithmetic so a 40% meeting haircut on
already-observed Jira velocity cannot hide. When interrupt was not retrieved,
say fillable is an upper bound and do not claim a 0% interrupt rate.
What ships with it
3 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.
- 12d ago First seen · 60 lines · 195 tokens per session scan A 0972e9fde903
rhdh-release-capacity-plan is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 195 tokens to every session and 804 once invoked, about $0.0008 per session on Opus 5.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-10-09.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.