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 agentmods add skills/bmbouter/redhat-agents/dependency-mappernpx skills add bmbouter/redhat-agents --skill dependency-mappergit clone --depth 1 https://github.com/bmbouter/redhat-agentsWhat 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 | $0.00027 | $0.00499 |
| Opus 5 | $0.00014 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
dependency-mapper 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 2d 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 understand what's blocking what, before planning, or when a critical issue is blocked and they need to trace the chain.
Instructions
Read local/jira-workflow.md to understand blocking conventions (flags, issue links, or both).
1. Determine scope
Ask the PO:
- All active issues? A specific epic? A specific blocked ticket?
- Cross-project dependencies too, or just within this project?
2. Query dependencies
Blocked issues:
project = <PROJECT> AND cf[10517] = "True" ORDER BY priority ASC
(Adjust based on workflow config.)
For each blocked issue, retrieve its issue links to find what's blocking it. Then check if the blocker is itself blocked — trace the full chain.
Also check parent-child relationships: if all sub-issues of an epic are blocked, the epic is effectively blocked even without a flag.
3. Build dependency map
For each dependency chain:
ISSUE-100 (Blocker, In Progress)
└── blocks → ISSUE-200 (Blocked, Major)
└── blocks → ISSUE-300 (Blocked, Critical)
└── blocks → ISSUE-400 (Blocked, Critical)
4. Identify high-impact blockers
Rank blockers by how many downstream issues they affect:
## Dependency Report — <date>
### Highest-Impact Blockers
| Blocker | Status | Assignee | Downstream Issues | Downstream Priority |
|---------|--------|----------|-------------------|---------------------|
| ISSUE-100 | In Progress | @alice | 3 | 2 Critical, 1 Major |
| ISSUE-567 | New | unassigned | 2 | 1 Major, 1 Normal |
### Dependency Chains
[Show each chain as a tree, as above]
### Unblocking Recommendations
- ISSUE-100: Assigned, in progress — check with @alice on ETA
- ISSUE-567: **Unassigned and New** — needs immediate attention, blocking 2 issues
### Orphaned Blocks
[Issues marked as blocked but with no blocking link — may be stale]
Present to the PO with recommended unblocking actions.
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.
- 2d ago First seen · 68 lines · 27 tokens per session scan A 9dad8f5e129f
dependency-mapper is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 499 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…