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 agentmods add skills/leolin990405/r-analytics-skill/data.tablenpx skills add LeoLin990405/r-analytics-skill --skill data.tablegit clone --depth 1 https://github.com/LeoLin990405/r-analytics-skillWhat 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 | $0.00022 | $0.01001 |
| Opus 5 | $0.00011 | $0.00500 |
| Sonnet 5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
data.table 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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
data.table
High-performance data manipulation.
Basics
library(data.table)
# Create
dt <- data.table(x = 1:5, y = letters[1:5])
dt <- as.data.table(df)
# Syntax: dt[i, j, by]
# i = row filter
# j = column select/compute
# by = group by
Row Operations (i)
# Filter rows
dt[x > 3]
dt[x > 3 & y == "a"]
dt[x %in% c(1, 2, 3)]
dt[x %between% c(2, 4)]
dt[y %like% "^a"]
# Order
dt[order(x)]
dt[order(-x)]
dt[order(x, -y)]
# First/last rows
dt[1:5]
dt[.N] # Last row
dt[(.N-4):.N] # Last 5 rows
Column Operations (j)
# Select columns
dt[, .(x, y)]
dt[, x] # Returns vector
dt[, .(x)] # Returns data.table
dt[, c("x", "y"), with = FALSE]
# Compute
dt[, .(mean_x = mean(x), sum_y = sum(y))]
dt[, .(total = x + y)]
# Modify in place (:=)
dt[, z := x * 2]
dt[, c("a", "b") := .(x + 1, y)]
dt[, `:=`(a = x + 1, b = y)]
# Remove columns
dt[, z := NULL]
dt[, c("a", "b") := NULL]
# Special symbols
dt[, .N] # Number of rows
dt[, .I] # Row indices
dt[, .SD] # Subset of data
dt[, .SDcols] # Columns in .SD
Grouping (by)
# Group by
dt[, .(mean = mean(x)), by = category]
dt[, .(mean = mean(x)), by = .(cat1, cat2)]
# keyby (sorted)
dt[, .(mean = mean(x)), keyby = category]
# .SD operations
dt[, lapply(.SD, mean), by = category]
dt[, lapply(.SD, mean), by = category, .SDcols = c("x", "y")]
dt[, lapply(.SD, mean), by = category, .SDcols = is.numeric]
# .N by group
dt[, .N, by = category]
Keys and Joins
# Set key
setkey(dt, id)
setkeyv(dt, c("id1", "id2"))
# Join
dt1[dt2, on = "id"] # Right join
dt2[dt1, on = "id"] # Left join
dt1[dt2, on = "id", nomatch = 0] # Inner join
# Multiple keys
dt1[dt2, on = .(a, b)]
dt1[dt2, on = .(a = x, b = y)]
# Non-equi joins
dt1[dt2, on = .(x >= a, x <= b)]
# Rolling joins
dt1[dt2, on = "date", roll = TRUE]
dt1[dt2, on = "date", roll = "nearest"]
Reshaping
# Wide to long
melt(dt, id.vars = "id", measure.vars = c("a", "b"))
# Long to wide
dcast(dt, id ~ variable, value.var = "value")
dcast(dt, id ~ variable, fun.aggregate = mean)
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.
- 3d ago First seen · 155 lines · 22 tokens per session scan A 8273fad3e8dc
data.table is a skill published in the GitHub repository LeoLin990405/r-analytics-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 1,001 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
ask-zilliz
Zilliz Cloud onboarding and usage assistant. Helps users understand Zilliz Cloud, choose the right plan, estimate costs, write code, debug issues, and adopt new features like Functions, Volumes, and Global Clusters. Use this skill whenever the user asks about Zilliz Cloud — including plan selection, pricing, cost…
external-collection
Use when the user wants to trigger, describe, or list refresh jobs for an external collection (a collection backed by an external data source such as Vector Lake). Note this is the data-plane refresh workflow, not collection CRUD -- for create/drop/load see the collection skill.
on-demand-cluster
Use when the user wants to create, list, describe, or delete an on-demand (Vector Lake / VectorLake) cluster. On-demand clusters auto-suspend after an idle TTL and are intended for ad-hoc query workloads against a Vector Lake.
vector
Use when the user wants to search, query, insert, upsert, get, or delete vectors in a Milvus collection.
index
Use when the user wants to create, list, describe, or drop indexes on Milvus collections.
data-science-expert
Expert-level data science, analytics, visualization, and statistical modeling.