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-config-eventsgit 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-events)<a href="https://agentmods.dev/skills/treasure-data/td-skills/rt-config-events"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config-events/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-events"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config-events.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.00028 | $0.01918 |
| Opus 5.5 | $0.00011 | $0.00767 |
| Sonnet 5.5 | $0.00006 | $0.00384 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
rt-config-events 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RT 2.0 Event Configuration
Configure event tables and key events for real-time processing.
Prerequisites
- RT 2.0 enabled (use
rt-config-setupskill first) - Streaming event tables with data
- Event table schema knowledge
Event Table Structure
events:
- name: "page_view" # Event identifier
database: "events_db" # Database name
table: "web_events" # Table name
filter: # Optional: filter events
field: "td_path" # Field to filter on
pattern: "^/pageview/" # Regex pattern
description: "Page view events" # Optional
- name: "purchase"
database: "events_db"
table: "commerce_events"
filter:
field: "event_type"
pattern: "^purchase$"
description: "Purchase completion events"
Event Filters
Filter events using regex patterns:
Common Patterns
# Exact match
filter:
field: "event_type"
pattern: "^purchase$"
# Starts with
filter:
field: "td_path"
pattern: "^/cart/add"
# Contains
filter:
field: "url"
pattern: ".*product.*"
# Multiple options (OR)
filter:
field: "event_type"
pattern: "^(purchase|add_to_cart|checkout)$"
# No filter (all events)
# Omit filter section
Field Selection
Common fields to filter on:
td_path- Event path/name from SDKevent_type- Custom event type fieldevent_name- Event name fieldaction- Action field- Custom fields in your event table
Discover Event Tables
# List databases
tdx databases --json
# List tables in database
tdx tables list events_db --json
# View table schema
tdx table describe events_db web_events
# Preview events
tdx query "select * from events_db.web_events limit 10"
# Check event types
tdx query "
select
td_path,
event_type,
count(*) as event_count
from events_db.web_events
where td_interval(time, '-1d')
group by td_path, event_type
order by event_count desc
limit 20
"
# Check field values for filtering
tdx query "
select distinct td_path
from events_db.web_events
where td_interval(time, '-1d')
limit 50
"
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 · 323 lines · 28 tokens per session scan A 33a71e5096b3
rt-config-events is a skill published in the GitHub repository treasure-data/td-skills (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,918 once invoked, about $0.0001 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-events compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rt-config-eventstreasure-data/td-skills | Skill | 22 | 5d ago | Apache-2.0 | A | 28 | 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 |