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 treasure-data/td-skills --skill rt-configgit clone --depth 1 https://github.com/treasure-data/td-skillsWrote 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/treasure-data/td-skills/rt-config)<a href="https://agentmods.dev/skills/treasure-data/td-skills/rt-config"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config/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/treasure-data/td-skills/rt-config"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00039 | $0.02306 |
| Opus 5.5 | $0.00016 | $0.00922 |
| Sonnet 5.5 | $0.00008 | $0.00461 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
rt-config 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 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.
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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RT 2.0 Configuration
Configure real-time personalization for parent segments: event tables, RT attributes, batch attributes, and ID stitching.
Prerequisites
tdxCLI installed and authenticated- Parent segment created in Data Workbench
- RT 2.0 enabled by CSM (contact CSM if not enabled)
- Streaming event tables configured and receiving data
Quick Start
# Check RT status
tdx ps view <parent_segment_id> --json
# Initialize configuration template
tdx ps pz init <parent_segment_id> -o rt_config.yaml
# Validate configuration
tdx ps rt validate rt_config.yaml
# Push configuration
tdx ps push rt_config.yaml
Configuration Structure
parent_segment_id: "394649"
# Event tables to track
events:
- name: "page_view"
database: "events_db"
table: "web_events"
filter:
field: "td_path"
pattern: "^/pageview/"
- name: "purchase"
database: "events_db"
table: "commerce_events"
filter:
field: "event_type"
pattern: "^purchase$"
# Real-time attributes
attributes:
# Single - Latest value
- name: "last_product_viewed"
type: "single"
source_event: "page_view"
source_field: "product_id"
aggregation: "last"
sensitivity: "non-sensitive"
# List - Array with expiry
- name: "viewed_products_30d"
type: "list"
source_event: "page_view"
source_field: "product_id"
aggregation: "distinct_list"
max_items: 50
expiry_days: 30
sensitivity: "non-sensitive"
# Counter - Event counts
- name: "purchase_count_7d"
type: "counter"
source_event: "purchase"
window_duration: "7d"
aggregation: "count"
sensitivity: "non-sensitive"
# Imported batch - From parent segment
- name: "customer_tier"
type: "imported_batch"
source: "parent_segment"
sensitivity: "non-sensitive"
# ID stitching
id_stitching:
primary_key: "td_client_id"
stitching_keys:
- name: "td_client_id"
exclude_regex: "^test_.*"
- name: "email"
exclude_regex: ".*@test\\.com$"
- name: "user_id"
ext_lookup_key: "email"
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 · 369 lines · 39 tokens per session scan A 5dfcd9899d76
rt-config is a skill published in the GitHub repository treasure-data/td-skills (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,306 once invoked, about $0.0002 per session on Opus 5.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.
rt-config compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rt-configtreasure-data/td-skills | Skill | 22 | 5d ago | Apache-2.0 | A | 39 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 3d ago | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 6d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |