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-sosgit 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-sos)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-release-sos"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-sos/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-sos"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-release-sos.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.00093 | $0.00478 |
| Opus 5.5 | $0.00037 | $0.00191 |
| Sonnet 5.5 | $0.00019 | $0.00096 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
rhdh-release-sos 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 27d 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
RHDH release SoS check-in
Produce the cumulative release check-in a Scrum of Scrums call needs: where the release sits on the calendar, which checklist rows are due today, and the Jira counts behind them. Read-only — the report is copied into the meeting; nothing is posted.
Route
Load workflows/sos-report.md. The runbook lives in references/sos-checks.md;
timeline rules in references/timeline.md; output shape in
references/report-format.md.
Boundary with the neighbouring skills
- Milestone dates on their own —
/rhdh-release-schedule. - Ad-hoc counts without the SoS runbook —
/rhdh-release-status. - Team roster and Slack handles —
/rhdh-release-teams. - Slack freeze announcements —
/rhdh-release-announce. - Rich Filter setup prose —
/rhdh-release-status(references/config.mdthere).
Query execution reuses the /rhdh-release-status scripts through
scripts/_release_bridge.py; install both skills together.
Completion
Complete when the user receives report_markdown from the CLI unchanged in chat,
and a self-contained HTML file exists at report_html_path (written by every
run, not plan): metadata table, milestone table, Checks rows, and team
sub-rows as in the markdown report. Nothing was posted to Slack or Jira.
What ships with it
18 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.
- agents/openai.yaml 127 B
- references/config.md 920 B
- references/report-format.md 2.2 KB
- references/report-template-html.md 1.9 KB
- references/report-template.md 1.7 KB
- references/sos-checks.md 16 KB
- references/timeline.md 1.4 KB
- reports/.gitignore 7 B
- reports/.gitkeep 0 B
- scripts/_release_bridge.py 988 B runs code
- scripts/sos_checks.py 6.6 KB runs code
- scripts/sos_due.py 1.4 KB runs code
- scripts/sos_expect.py 3.0 KB runs code
- scripts/sos_metrics.py 1.9 KB runs code
- scripts/sos_report_format.py 22 KB runs code
- scripts/sos_report.py 24 KB runs code
- scripts/sos_testplan.py 5.2 KB runs code
- workflows/sos-report.md 3.3 KB
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.
- 27d ago First seen · 42 lines · 93 tokens per session scan A f2844bb1b2f9
rhdh-release-sos is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 478 once invoked, about $0.0004 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-09-24.
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.