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-attributesgit 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-attributes)<a href="https://agentmods.dev/skills/treasure-data/td-skills/rt-config-attributes"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config-attributes/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-attributes"><img src="https://agentmods.dev/badge/skills/treasure-data/td-skills/rt-config-attributes.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.00027 | $0.02560 |
| Opus 5.5 | $0.00011 | $0.01024 |
| Sonnet 5.5 | $0.00005 | $0.00512 |
| Haiku 4.5 | $0.00003 | $0.00256 |
Grade A, and why
rt-config-attributes 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RT 2.0 Attribute Configuration
Configure real-time and batch attributes for profile enrichment.
Prerequisites
- RT 2.0 enabled and event tables configured
- Use
rt-config-eventsskill to configure events first
Attribute Types
Single Attributes
Latest or aggregated value from event field:
- name: "last_product_viewed"
type: "single"
source_event: "page_view"
source_field: "product_id"
aggregation: "last" # last, first, sum, min, max
sensitivity: "non-sensitive" # or "sensitive" for PII
description: "Most recently viewed product"
Aggregation options:
last- Most recent valuefirst- First value seensum- Sum of valuesmin- Minimum valuemax- Maximum value
List Attributes
Distinct values with expiry:
- name: "viewed_products_30d"
type: "list"
source_event: "page_view"
source_field: "product_id"
aggregation: "distinct_list"
max_items: 50 # Max list size
expiry_days: 30 # Remove items after N days
sensitivity: "non-sensitive"
description: "Products viewed in last 30 days"
Parameters:
max_items- Maximum list length (default: 100)expiry_days- Days before items expire (default: 90)- Only
distinct_listaggregation supported
Counter Attributes
Event counts over time window:
- name: "purchase_count_7d"
type: "counter"
source_event: "purchase"
window_duration: "7d" # 24h, 7d, 30d, 90d
aggregation: "count" # count or sum
sensitivity: "non-sensitive"
description: "Purchases in last 7 days"
With field sum:
- name: "total_spend_30d"
type: "counter"
source_event: "purchase"
source_field: "amount" # Field to sum
window_duration: "30d"
aggregation: "sum"
sensitivity: "non-sensitive"
Window options: 24h, 7d, 30d, 90d
Imported Batch Attributes
From parent segment (updated on schedule):
- name: "customer_tier"
type: "imported_batch"
source: "parent_segment"
sensitivity: "non-sensitive"
description: "Customer tier from parent segment"
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 · 389 lines · 27 tokens per session scan A 62b06735bd6e
rt-config-attributes is a skill published in the GitHub repository treasure-data/td-skills (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,560 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-attributes compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rt-config-attributestreasure-data/td-skills | Skill | 22 | 5d ago | Apache-2.0 | A | 27 | Claude Code |
| agent-platform-model-registrygoogle/skills | Skill | 24k | today | Apache-2.0 | A | 60 | Claude Code, Codex |
| foundry-config-setupmicrosoft/agent-framework | Skill | 15k | today | MIT | A | 65 | Claude Code, Codex |
| google-cloud-solution-agentic-analytics-spark-knowledge-cataloggoogle/skills | Skill | 24k | today | Apache-2.0 | A | 132 | Claude Code, Codex |
| training-checkwanshuiyin/Auto-claude-code-research-in-sleep | Skill | 19k | yesterday | MIT | A | 35 | Claude Code |
| nemo-automodel-launcher-configNVIDIA/skills | Skill | 3.9k | today | Apache-2.0 | A | 30 | Claude Code |
| finetuningmicrosoft/skills | Skill | 3.2k | today | MIT | A | 132 | Claude Code |