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 LeoLin990405/r-analytics-skill --skill r-ml-deeplearninggit clone --depth 1 https://github.com/LeoLin990405/r-analytics-skillWrote 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/leolin990405/r-analytics-skill/r-ml-deeplearning)<a href="https://agentmods.dev/skills/leolin990405/r-analytics-skill/r-ml-deeplearning"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/r-ml-deeplearning/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/leolin990405/r-analytics-skill/r-ml-deeplearning"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/r-ml-deeplearning.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.00034 | $0.01145 |
| Opus 5 | $0.00017 | $0.00573 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
r-ml-deeplearning 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 8d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
R Deep Learning
Neural networks with torch and keras.
torch (PyTorch-like)
library(torch)
# Tensors
x <- torch_tensor(matrix(1:6, 2, 3))
x$shape
x$dtype
# Operations
y <- x + 1
z <- torch_matmul(x, x$t())
# GPU
if (cuda_is_available()) {
x <- x$cuda()
}
# Define model
net <- nn_module(
initialize = function(input_size, hidden_size, output_size) {
self$fc1 <- nn_linear(input_size, hidden_size)
self$fc2 <- nn_linear(hidden_size, output_size)
},
forward = function(x) {
x %>%
self$fc1() %>%
nnf_relu() %>%
self$fc2()
}
)
model <- net(input_size = 10, hidden_size = 64, output_size = 2)
# Training loop
optimizer <- optim_adam(model$parameters, lr = 0.001)
criterion <- nn_cross_entropy_loss()
for (epoch in 1:100) {
optimizer$zero_grad()
output <- model(x_train)
loss <- criterion(output, y_train)
loss$backward()
optimizer$step()
if (epoch %% 10 == 0) {
cat("Epoch:", epoch, "Loss:", loss$item(), "\n")
}
}
# Predictions
model$eval()
with_no_grad({
pred <- model(x_test)
})
luz (High-level torch)
library(luz)
# Define model
model <- nn_module(
initialize = function(input_size) {
self$net <- nn_sequential(
nn_linear(input_size, 128),
nn_relu(),
nn_dropout(0.3),
nn_linear(128, 64),
nn_relu(),
nn_linear(64, 1)
)
},
forward = function(x) {
self$net(x)
}
)
# Train with luz
fitted <- model %>%
setup(
loss = nn_mse_loss(),
optimizer = optim_adam,
metrics = list(luz_metric_mae())
) %>%
set_hparams(input_size = ncol(x_train)) %>%
fit(
data = list(x_train, y_train),
valid_data = list(x_valid, y_valid),
epochs = 100,
callbacks = list(
luz_callback_early_stopping(patience = 10),
luz_callback_lr_scheduler(lr_one_cycle, max_lr = 0.01)
)
)
# Predictions
pred <- predict(fitted, x_test)
keras/tensorflow
library(keras)
# Sequential model
model <- keras_model_sequential() %>%
layer_dense(units = 128, activation = "relu", input_shape = c(10)) %>%
layer_dropout(rate = 0.3) %>%
layer_dense(units = 64, activation = "relu") %>%
layer_dense(units = 1, activation = "sigmoid")
# Compile
model %>% compile(
loss = "binary_crossentropy",
optimizer = optimizer_adam(learning_rate = 0.001),
metrics = c("accuracy")
)
# Train
history <- model %>% fit(
x_train, y_train,
epochs = 100,
batch_size = 32,
validation_split = 0.2,
callbacks = list(
callback_early_stopping(patience = 10),
callback_reduce_lr_on_plateau(factor = 0.1, patience = 5)
)
)
# Evaluate
model %>% evaluate(x_test, y_test)
# Predictions
pred <- model %>% predict(x_test)
# Save/load
save_model_hdf5(model, "model.h5")
model <- load_model_hdf5("model.h5")
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 185 lines · 34 tokens per session scan A 1a39322085a7
r-ml-deeplearning is a skill published in the GitHub repository LeoLin990405/r-analytics-skill (5 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 1,145 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
model-registry-refresh
Re-verify and extend catalog/model-registry.json — the fail-closed model-name and reasoning-effort matrix scripts/model-policy.mjs validates against — via delegated Context7-backed research, orchestrator-owned registry edits, and the full validation chain; use when a policy check fails on an unregistered model, a…
databricks-ai-bi-genie
Use this skill to statically review AI/BI Genie agent and dashboard design: agent scoping (30-table limit), instructions and trusted assets, metric-view correctness, dashboard limits and rendering, benchmark design and honest accuracy reading, and the critical 'Individual data' versus 'Share data' permission decision.…
databricks-data-quality-observability
Use this skill to design and verify data quality expectations, table constraints, Lakehouse Monitoring, freshness detection, event-log interrogation, quality SLAs, and downstream quality signaling for Lakeflow pipelines. Reads pipeline source, table schema, expectations, monitor configuration, and event-log queries…
databricks-genai-agent-engineering
Use this skill to review generative-AI agent design on Databricks: Mosaic AI Agent Framework and ResponsesAgent interface, Databricks AI Search index variant and sync-mode choice, retrieval and context engineering, MCP server category and trust boundaries, external model-provider selection, and Unity AI Gateway…
databricks-genai-evaluation-observability
Use this skill to review generative-AI evaluation, tracing, and observability design on Databricks: MLflow Tracing instrumentation and span design, trace storage and governance, mlflow.genai.evaluate() harness design, the judge-versus-scorer distinction, built-in judge selection (ten single-turn and seven multi-turn)…
databricks-lakeflow-pipeline-engineering
Use this skill to design Lakeflow Spark Declarative Pipelines: medallion layering, Lakeflow Jobs orchestration and task dependencies, Delta table layout (liquid clustering, deletion vectors, Predictive Optimization), Auto Loader ingestion, schema evolution and rescueddata, materialized views versus streaming tables…