rudder-data-graphs

rudder-data-graphs is a skill for Claude Code from rudderlabs/rudder-agent-skills. It costs 40 tokens per session (4,516 once invoked), scanned A, original, MIT.

A data-mapping guide that turns RETL customer-data sources into Data Graph YAML for RudderStack Audiences. It also lists available sources, possible audience segments, warehouse details, and follow-up actions.

In plain words
What is it for?
Use it to inspect a customer’s workspaces and RETL sources, map data to audience entities and events, design graphs, prepare a demo warehouse, and identify next steps.
Why use it?
It reduces the manual work of finding relevant data, understanding its structure, and deciding how that data should represent customers, events, and audiences.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the rudder-core plugin — 9 skills shipped together

Good fit Use it to inspect a customer’s workspaces and RETL sources, map data to audience entities and events, design graphs, prepare a demo warehouse, and identify next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rudderlabs/rudder-agent-skills/rudder-data-graphs
Install

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.

Any agent
npx skills add rudderlabs/rudder-agent-skills --skill rudder-data-graphs
Clone the repo
git clone --depth 1 https://github.com/rudderlabs/rudder-agent-skills

Made for: Claude Code.

Or install rudder-core, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for rudder-data-graphs

README.md
[![agentmods](https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs/github.svg)](https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs)
Your own site
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs/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.

agentmods 80×15 button for rudder-data-graphs

Your own site · 80×15
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-data-graphs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.04516
Opus 5 $0.00020 $0.02258
Sonnet 5 $0.00008 $0.00903
Haiku 4.5 $0.00004 $0.00452

Measured 12d ago against content hash 957de8a2c5ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

rudder-data-graphs 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.

plugins/rudder-core/skills/rudder-data-graphs/SKILL.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RETL Connection Analysis & Data Graph Design

What this skill produces

Given a customer name (or workspace / org identifier), this skill produces five deliverables, in order:

  1. Source Inventory — every relevant RETL source categorized as entity / event / audience / supporting-only.
  2. Untapped Segment List — realistic, filterable business dimensions the customer has not yet expressed as audiences.
  3. Data Graph YAML — one per workspace / domain, ready for validation in rudder-cli or the visual builder.
  4. Demo Warehouse Spec — tables, key columns, joins, and known / inferred schema details needed to mock the graph.
  5. Action Items — priority-ordered next steps, including the upgrade narrative and any assumptions to confirm.

The end-to-end flow is: find workspaces → list RETL sources → shortlist relevant sources → fetch full configs for the shortlist → categorize → design graph → validate → hand off. Each step below says what to do and why, so you can adapt when the customer doesn't match the common shapes.


Step 1 — Find the customer's workspaces

  1. admin_search_organizations(company_name=...) to get the org_id.
  2. admin_search_workspaces(search_by=organizationId) using that id.
  3. Keep only status=ACTIVE workspaces. Why: inactive workspaces often have stale or disconnected configs and will produce misleading source lists.
  4. Note the likely warehouse-backed workspaces, but do not assume you already have the correct accountId at this stage. Why: the Data Graph YAML embeds account_id, and that value is the warehouse account the graph runs against. The most authoritative source for it is rudder-cli workspace accounts list --json (see Step 4a); a RETL source config is a convenient secondary hint when one already exists, but it is not a prerequisite.

Step 2 — Discover sources, anchored on audiences

Run list_sources(workspace_id=..., retl_type=all, includeConfig=false) per workspace. Why includeConfig=false: full configs blow the context budget on large workspaces; start broad, then fetch detail only for sources you actually need.

Read the full file on GitHub · 289 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 289 lines · 40 tokens per session scan A 957de8a2c5ff

Subscribe to this mod's changes

rudder-data-graphs is a skill published in the GitHub repository rudderlabs/rudder-agent-skills (18 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 4,516 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.

Related

Other skills, from other repositories

scientific-figure-prompt-compiler

Transform concise scientific or technical descriptions into structured visual specifications and high-quality image-generation prompts. Use for scientific figures, technical diagrams, system architectures, mechanisms, workflows, spatial models, timelines, layered systems, and information-dense visuals. Model-agnostic…

basejb/skills · 72 tokens

seo-optimizer

Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.

basejb/skills · 60 tokens

ai-collab-evaluator

A review of Claude Code session logs against four hiring criteria for working with AI: how you handle, use, and question AI, and how you weigh trade-offs.

basejb/skills · 169 tokens

learning-companion

A guided learning tool that turns official documents or other sources into lasting study notes through five stages, including explanation, recall, reflection, and next steps.

basejb/skills · 134 tokens

oss-tour

A guided method for learning an unfamiliar open-source repository in layers, from the whole project to folders and core modules. An open-source repository is a publicly available code project whose source can be inspected.

basejb/skills · 106 tokens

image-optimizer

An image-processing tool that converts images to WebP, an image format that can reduce file size while preserving visual quality. It handles individual images, groups of images, and whole directories.

basejb/skills · 43 tokens