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-et/rhdp-rca-plugin --skill logs-fetchergit 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/logs-fetcher)<a href="https://agentmods.dev/skills/redhat-et/rhdp-rca-plugin/logs-fetcher"><img src="https://agentmods.dev/badge/skills/redhat-et/rhdp-rca-plugin/logs-fetcher/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-et/rhdp-rca-plugin/logs-fetcher"><img src="https://agentmods.dev/badge/skills/redhat-et/rhdp-rca-plugin/logs-fetcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01677 |
| Opus 5 | $0.00032 | $0.00839 |
| Sonnet 5 | $0.00013 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
log-fetcher 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 9d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Fetcher
Fetch available logs for further investigations. Currently
[Python] Fetch logs via SSH
Quick Start
cd /path/to/incident-investigator
pip install -r requirements.txt
python -m scripts.cli new --incident-id "inc-001"
python -m scripts.cli run --incident-id "inc-001" --all
python -m scripts.cli status --incident-id "inc-001"
Prerequisites
We assume that the user has correctly set up the SSH profile to the Ansible server.
Fetch Ansible Logs via SSH
Input: User provides incident context (time window, job IDs, or investigation scope)
Output: Raw log files in local directory (default: ~/etl-logs)
Scripts: scripts/fetch_logs_ssh.py or scripts/fetch_logs_by_job.py
Prerequisites
Ensure SSH access is configured:
ssh ${REMOTE_HOST} # Should connect without password prompt
Option A: Fetch by Time/Mode (fetch_logs_ssh.py)
Use this when you want to fetch recent logs or a range of logs based on time.
-
Determine the scope:
- For recent failures: Use
--mode processed --order desc --limit 10-50 - For specific time window: Use
--start-timeand/or--end-timeto filter by creation date - For all recent activity: Use
--mode all(includes both processed and ignored)
- For recent failures: Use
-
Run the fetch script:
# Fetch recent logs with limit python -m scripts.fetch_logs_ssh \ --mode processed \ --order desc \ --limit 20 \ --local-dir .incidents/<incident-id>/raw_logs # Fetch logs within a specific time range python -m scripts.fetch_logs_ssh \ --mode processed \ --start-time "2025-12-09 08:00:00" \ --end-time "2025-12-10 17:00:00" \ --local-dir .incidents/<incident-id>/raw_logs # Fetch logs from a specific day python -m scripts.fetch_logs_ssh \ --mode all \ --start-time "2025-12-10" \ --end-time "2025-12-10" \ --local-dir .incidents/<incident-id>/raw_logs -
Parameters:
--mode: Select log type (processed,ignored, orall)--order: Sort by time (desc= newest first,asc= oldest first)--limit: Number of files to fetch (omit for all files)--start-time: Filter logs created on or after this time (format:YYYY-MM-DD [HH:MM[:SS]])--end-time: Filter logs created on or before this time (format:YYYY-MM-DD [HH:MM[:SS]])--local-dir: Where to store logs (default:~/etl-logs)
What ships with it
2 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.
- 9d ago First seen · 174 lines · 65 tokens per session scan A 0e63ccba4b24
log-fetcher is a skill published in the GitHub repository redhat-et/rhdp-rca-plugin (10 stars, last pushed 14d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,677 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…