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/redhat-et/rhdp-rca-plugin/rca-annotatornpx skills add redhat-et/rhdp-rca-plugin --skill rca-annotatorgit clone --depth 1 https://github.com/redhat-et/rhdp-rca-pluginWrote 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-et/rhdp-rca-plugin/rca-annotator)<a href="https://agentmods.dev/skills/redhat-et/rhdp-rca-plugin/rca-annotator"><img src="https://agentmods.dev/badge/skills/redhat-et/rhdp-rca-plugin/rca-annotator.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.02168 |
| Opus 5 | $0.00017 | $0.01084 |
| Sonnet 5 | $0.00007 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
rca-annotator 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 4d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RCA Annotator
A structured annotation tool that presents the root-cause-analysis agent's diagnosis to the user and guides them through labeling it — capturing whether the diagnosis is correct, evidence quality, difficulty, and alternative hypotheses.
root-cause-analysis (Agent) |
rca-annotator (Annotation tool) |
|
|---|---|---|
| Purpose | Diagnose failures for users | Capture human-labeled ground-truth data |
| Reads | Logs, Splunk, GitHub (live) | Step 1/3/4/5 output files (offline) |
| Output | Human-readable diagnosis | Structured annotation.json |
Use when: a root-cause-analysis run is complete and you want to annotate its output as correct, incorrect, or partially correct — for evaluation, benchmarking, or dataset building.
Do NOT use to perform initial RCA (use root-cause-analysis).
Prerequisites
Verify root-cause-analysis has been completed.
JUMPBOX_URI(optional) — SSH connection string (e.g."user@host -p 2222"). If unset, uses local.analysis/only.- SSH keys configured in
~/.ssh/configif using jumpbox;sshandrsyncinstalled. - Required files in
.analysis/<job_id>/:step5_summary.json— Agent's final diagnosis (primary input)step1_job_context.json— Job metadata, failed tasksstep3_correlation.json— Timeline with AAP + Splunk eventsstep4_github_fetch_history.json— Configuration and code context
If missing, run root-cause-analysis skill first.
Workflow
- Download from jumpbox (if
JUMPBOX_URIset) or verify local files - Read
step5_summary.json— present the agent's diagnosis to the user - Walk through annotation questions interactively — the user labels each section
- Write
annotation.jsonwith the user's labels - Upload to jumpbox (if
JUMPBOX_URIset)
Step 0: Download Analysis Files
cd skills/rca-annotator
python scripts/cli.py download --job-id <job_id>
Downloads from jumpbox /usr/local/mlflow/<job_id>/ to local .analysis/<job_id>/. If JUMPBOX_URI unset, validates local files only. Errors on missing remote directory, missing required files, or connection failure.
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.
- 4d ago First seen · 253 lines · 35 tokens per session scan A 91992ffe24d3
rca-annotator is a skill published in the GitHub repository redhat-et/rhdp-rca-plugin (10 stars, last pushed 10d ago), licensed Apache-2.0. It adds 35 tokens to every session and 2,168 once invoked, about $0.0002 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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…