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 activationsgit 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/activations)<a href="https://agentmods.dev/skills/treasure-data/td-skills/activations"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/activations/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/activations"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/activations.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.00013 | $0.00846 |
| Opus 5.5 | $0.00005 | $0.00338 |
| Sonnet 5.5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
activations 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activations
Treasue Data's real time services include digital marketing activations. These are sent to various destinations. This skill can be used to query the database table that stores activations logs for both successful and failed activations, which is a source of useful information for the digital marketer.
Description
Requirements
In order to query the activation log we must know the parent segment the customer is interested in. A customer may have a number of parent segments so we must ask them to provide the one they are interested before making a query. A segment ID will be a numeric value like 411671.
The user must also have a correctly configured Treasure Data mcp server to enable the database lookup @treasuredata/mcp-server
In addition the api key with appropriate access to the database table should be available and configured.
Database
The database name contains the parent segment ID and has this format cdp_audience_394649_rt. This is where you can plug in the parent segment the user gives in the request.
Activations table
The activation log table is always called activations and is in the Parent Segment real time database.
Schema
The activations table has the following schema. The format is of the schema below is:
- Schema column index (example 1)
- Column name (example time)
- Query Column name (example time) (generally can be ignored for activations)
- Data type (string, time, int)
1 time time int 2 delivered delivered string
3 status status long
4 timestamp timestamp long
5 activation_type activation_type string
6 log_time log_time long
7 journey_name journey_name string
8 journey_stage_name journey_stage_name string
9 activation_name activation_name string
10 rid rid string
11 error error string
12 activation_id activation_id string
13 event_id event_id string
14 response response string
For the purposes of making queries and talking about activations with the user here are the meanings of the columns.
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 · 134 lines · 13 tokens per session scan A 3eb19ddc51cd
activations is a skill published in the GitHub repository treasure-data/td-skills (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 13 tokens to every session and 846 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.
activations compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| activationstreasure-data/td-skills | Skill | 22 | 5d ago | Apache-2.0 | A | 13 | 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 |