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 Undertone0809/rudder --skill rudder-data-path-diagnostician-maintainergit 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/rudder-data-path-diagnostician-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/rudder-data-path-diagnostician-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-data-path-diagnostician-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/rudder-data-path-diagnostician-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-data-path-diagnostician-maintainer.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.00067 | $0.01679 |
| Opus 5 | $0.00034 | $0.00839 |
| Sonnet 5 | $0.00013 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
rudder-data-path-diagnostician-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 11d 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 -sS <base-url>/api/health How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rudder Data Path Diagnostician Maintainer
Use this skill when the user's real problem is that a Rudder surface does not show the data they expected.
The goal is to produce an evidence-backed data lineage and root cause, not to guess from the screenshot. Most failures in this class are caused by one of:
- wrong runtime or organization
- empty source records
- filtering or date-window mismatch
- derived data that is not generated from the records the user expected
- API/service aggregation gap
- UI rendering or state merge bug
- stale seed/demo assumptions
This skill also has an explanation mode. When the user asks "这个数据从哪来" or "现在的渲染逻辑是怎样的" and the data is no longer missing, explain the lineage from UI query to API route, service aggregation, derived records, and rendering states. In explanation mode, read-only source tracing may be enough; do not force database inspection when code and API contracts already answer the question.
Use When
Use this skill for questions like:
- "为什么 Calendar 没数据"
- "这个 Dashboard 怎么是空的"
- "prod z studio 下这里怎么没有 run / issue / calendar"
- "这个 UI 的数据从哪里来"
- "看起来应该有数据，但页面没有显示"
- "这个数字和数据库/API 对不上"
- "是不是 seed 数据没有写进去"
This skill is useful across dev, prod-local Desktop, worktree previews, and local production-style instances.
Do Not Use When
Do not use this skill for:
- a single agent run transcript failure; use
debug-run-transcript-maintainer - creating demo or screenshot data from scratch; use
mock-data-maintainer - pure UI polish where the data is already known; use
rudder-ui-polish-maintainer - CI, release, npm, Desktop packaging, or Chrome automation infrastructure
- destructive cleanup of organizations or databases unless the user explicitly authorizes that separate operation
Default Workflow
1. Confirm the symptom and target environment
Start by pinning down:
- surface: page, route, tab, card, chart, or screenshot region
- expected data: what the user believes should appear
- actual data: what is visible or returned
- runtime: dev, prod-local Desktop, worktree preview, or remote deployment
- organization: org id, URL key, display name, or selected org
- date window, filters, and selected project/agent when relevant
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.
- 11d ago First seen · 217 lines · 67 tokens per session scan A 6594fd53c5b6
rudder-data-path-diagnostician-maintainer is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,679 once invoked, about $0.0003 per session on Opus 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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.