Borrowing it
Nothing to install: this file belongs to Undertone0809/rudder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Undertone0809/rudder/main/.agents/skills/maintainer/debug-run-transcript-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/debug-run-transcript-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/debug-run-transcript-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/debug-run-transcript-maintainer/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/undertone0809/rudder/debug-run-transcript-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/debug-run-transcript-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 47 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00054 | $0.03158 |
| Opus 5.5 | $0.00022 | $0.01263 |
| Sonnet 5.5 | $0.00011 | $0.00632 |
| Haiku 4.5 | $0.00005 | $0.00316 |
Grade A, and why
debug-run-transcript-maintainer scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://127.0.0.1:3100/api/orgs How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Run Transcript
Analyze Rudder agent runs by reconstructing the execution story from the best available source.
Purpose
Runs fail for several different reasons:
- the model/runtime emitted an error
- the transcript parser missed useful structure
- the event stream is incomplete
- the stored excerpts are too shallow
- a tool call succeeded, but Rudder's message/run lifecycle marked the workflow failed during stream finalization, persistence, or UI status mapping
- the operator has only a partial run ID or limited context
This skill helps diagnose those cases without getting stuck on the wrong data source.
Debugging proves what happened in a run; it does not by itself prove that a product fix works. When a transcript diagnosis leads to a code, CLI, skill, runtime, or UI change, hand the work back to the lifecycle verification path and require product proof for the affected actor and terminal surface.
Source Priority
Always use sources in this order:
- Run-intelligence loader/API
- Best default.
- Reads run metadata, run events, and the underlying run log.
- Reconstructs transcript entries with runtime-specific parsers.
- Filesystem run log fallback
- Use when the local API is unavailable but run logs exist on disk.
- Good for transcript/tool-call reconstruction.
- Direct database queries
- Use only for targeted checks or when the first two paths are unavailable.
- DB rows alone are not the full transcript story.
Important Lessons / Known Traps
- Do not assume
~/.rudder/instances/dev/postgres-uriexists. In this repo it is not a reliable universal entrypoint. - Do not start with
heartbeat_run_eventsand assume they are the complete transcript. They are supplemental run events, not the full parsed execution trace. - Do not write
WHERE id LIKE 'prefix%'againstuuidcolumns. Cast first:id::text ILIKE 'prefix%'. - Do not assume
pnpm exec tsxworks from the repo root here. Prefer the repo-local launcher:
What ships with it
1 file 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.
- 2mo ago First seen · 371 lines · 54 tokens per session scan A 0d84d3ddb841
debug-run-transcript-maintainer is a skill published in the GitHub repository Undertone0809/rudder (294 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 3,158 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.