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-triggersgit 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-triggers)<a href="https://agentmods.dev/skills/treasure-data/td-skills/rt-triggers"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-triggers/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-triggers"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-triggers.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.00036 | $0.03122 |
| Opus 5.5 | $0.00014 | $0.01249 |
| Sonnet 5.5 | $0.00007 | $0.00624 |
| Haiku 4.5 | $0.00004 | $0.00312 |
Grade A, and why
rt-triggers 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "https://your-webhook.com/test" \ How it starts
The opening of the file, as written. The whole thing — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RT 2.0 Triggers (RT Journeys)
Create event-triggered journeys that activate in real-time when specific events occur, sending data to external systems.
Note: This skill is for RT Journeys (event-triggered, API-only). For stage-based Batch Journeys (YAML workflow with tdx journey), use the journey skill.
Journey Types
| Type | Entry | Workflow | Use Case |
|---|---|---|---|
| RT Journeys (this skill) | Event occurs | API-only | Real-time activations when events happen |
| Batch Journeys (journey skill) | Segment membership | YAML + tdx journey |
Multi-stage customer journey orchestration |
Prerequisites
- RT configuration complete (run
rt-configskill first) - RT status is "ok" (not "updating")
- Key events configured
- Webhook/activation endpoint ready (optional)
Quick Start
# Check RT status
tdx ps view <parent_segment_id> --json | jq '.realtime_config.status'
# List key events
tdx api "/audiences/<parent_segment_id>/realtime_key_events" --type cdp
# Create RT journey via API
tdx api "/entities/realtime_journeys" --type cdp --method POST --data '{
"name": "welcome_email",
"parent_segment_id": 394649,
"event_name": "registration",
"activations": [
{
"type": "webhook",
"endpoint": "https://your-app.com/webhooks/welcome",
"payload_template": {
"user_id": "{{user_id}}",
"event": "registration"
}
}
]
}'
RT Journey Structure
{
"name": "abandoned_cart_recovery",
"parent_segment_id": 394649,
"event_name": "cart_abandon",
"description": "Send webhook when cart is abandoned",
"activations": [
{
"type": "webhook",
"name": "cart_recovery_webhook",
"endpoint": "https://marketing-platform.com/webhooks/cart",
"method": "POST",
"headers": {
"Authorization": "Bearer {{api_key}}",
"Content-Type": "application/json"
},
"payload_template": {
"user_id": "{{user_id}}",
"cart_value": "{{cart_value}}",
"cart_items": "{{cart_items}}",
"event_time": "{{event_time}}"
}
}
],
"filters": {
"cart_value": {
"operator": "greater_than",
"value": 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 · 487 lines · 36 tokens per session scan A 11464a6d12db
rt-triggers is a skill published in the GitHub repository treasure-data/td-skills (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,122 once invoked, about $0.0001 per session on Opus 5.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.
rt-triggers compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rt-triggerstreasure-data/td-skills | Skill | 22 | 5d ago | Apache-2.0 | A | 36 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 69k | 3d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | today | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | today | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | today | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 573 | today | MIT | A | 105 | Claude Code, Codex |
| migrate-segw-to-raparc-mcp/arc-1 | Skill | 254 | today | MIT | A | 106 | Claude Code |