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 bmbouter/redhat-agents --skill status-reportgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/status-report)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/status-report"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/status-report/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/bmbouter/redhat-agents/status-report"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/status-report.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.00024 | $0.00451 |
| Opus 5.5 | $0.00010 | $0.00180 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
status-report 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 1mo 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
When to Use
When the PO needs to produce a status update for stakeholders, management, or the team.
Instructions
Read local/jira-workflow.md to understand statuses and conventions.
1. Ask about scope and format
- Time period: Last week? Last 2 weeks? Since a specific date?
- Audience: Team standup? Management? Stakeholders?
- Format: Slack message? Email? Confluence page?
- Focus: All work? Specific epics? Specific components?
2. Query Jira
Recently closed (shipped):
project = <PROJECT> AND status = Closed AND status changed to Closed after "<start_date>" ORDER BY resolved DESC
Currently in progress:
project = <PROJECT> AND status = "In Progress" ORDER BY priority ASC
Currently blocked:
project = <PROJECT> AND cf[10517] = "True" ORDER BY priority ASC
(Adjust the blocked query based on the workflow config's blocking mechanism.)
New issues filed in the period:
project = <PROJECT> AND created >= "<start_date>" ORDER BY created DESC
3. Generate report
Adapt the format to the audience:
For stakeholders / management:
## Status Report — <period>
### Completed
- [Brief description of key items shipped, grouped by epic if relevant]
### In Progress
- [Key items being worked on, with assignees]
### Blocked / At Risk
- [Blocked items with reason and what's needed to unblock]
### Metrics
- Closed: X issues
- Opened: Y issues
- Net: +/- Z
- Currently blocked: N
### Key Decisions Needed
- [Any items requiring stakeholder input]
For team Slack: Keep it concise — 5-10 lines max, bullet points, link to tickets.
Show the draft to the PO for review before sending or publishing.
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.
- 1mo ago First seen · 75 lines · 24 tokens per session scan A 615cd296a8c9
status-report is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 451 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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…