Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rudderlabs/rudder-agent-skillsnpx agentmods add skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-debuggingWrote 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/rudderlabs/rudder-agent-skills/rudder-instrumentation-debugging)<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-debugging"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-debugging/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/rudderlabs/rudder-agent-skills/rudder-instrumentation-debugging"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-debugging.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.00034 | $0.02123 |
| Opus 5 | $0.00017 | $0.01061 |
| Sonnet 5 | $0.00007 | $0.00425 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
rudder-instrumentation-debugging 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 12d 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instrumentation Debugging
This skill teaches how to diagnose and fix common validation errors, schema issues, and instrumentation problems when working with RudderStack data catalog and tracking plans.
Debugging Workflow
┌─────────────────┐
│ Error Occurs │
└────────┬────────┘
▼
┌─────────────────┐
│ Identify Type │ ← Validation? Schema? Runtime?
└────────┬────────┘
▼
┌─────────────────┐
│ Locate Source │ ← Which file? Which line?
└────────┬────────┘
▼
┌─────────────────┐
│ Understand Rule │ ← What does the validation expect?
└────────┬────────┘
▼
┌─────────────────┐
│ Fix & Validate │ ← Edit, then rudder-cli validate
└─────────────────┘
Common Validation Errors
Error: Reference Not Found
Error: data-catalog/events/product-viewed.yaml:15
Referenced property 'urn:rudder:property/proudct_id' not found
Cause: Typo in URN or property doesn't exist.
Fix:
# Wrong
- property: "urn:rudder:property/proudct_id" # Typo!
# Right
- property: "urn:rudder:property/product_id"
Debug steps:
# List all properties to find correct name
ls data-catalog/properties/
# Search for the property
grep -r "product" data-catalog/properties/
Error: Duplicate Resource Name
Error: Duplicate resource name 'Product Viewed' in kind 'event'
- data-catalog/events/ecommerce.yaml:5
- data-catalog/events/legacy.yaml:12
Cause: Same event name defined in multiple files.
Fix: Remove duplicate or rename one:
# Find duplicates
grep -r "name: \"Product Viewed\"" data-catalog/events/
Error: Invalid Config for Type
Error: data-catalog/properties/price.yaml:8
Config 'minLength' is not valid for type 'number'
Cause: Using string config options on a number type.
Fix:
# Wrong
spec:
name: "price"
type: "number"
config:
minLength: 1 # String config!
# Right
spec:
name: "price"
type: "number"
config:
minimum: 0 # Number config
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.
- 12d ago First seen · 361 lines · 34 tokens per session scan A 519fe837a91e
rudder-instrumentation-debugging is a skill published in the GitHub repository rudderlabs/rudder-agent-skills (18 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 2,123 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-30.
Other skills, from other repositories
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
diagnose
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
fix
Plan-aware auto-fix loop after coding. Runs tests, lint, format, and graph checks. Updates plan task status. Use after execute/tdd.
zoom-out
One-shot module map — go up a layer of abstraction and get a domain-vocabulary module map of the codebase. Use when lost in unfamiliar code, after a long deep-dive session, or when you need to re-orient before planning.
pdlc-perf
A workflow for finding and improving performance problems in a specified backend service or frontend application. It examines areas such as database queries, caching, response times, loading, rendering, and network use, then records its findings in a report.