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 stellarshenson/claude-code-plugins --skill datasetgit clone --depth 1 https://github.com/stellarshenson/claude-code-pluginsWrote 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/stellarshenson/claude-code-plugins/dataset)<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/dataset"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/dataset/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/stellarshenson/claude-code-plugins/dataset"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/dataset.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.00167 | $0.02183 |
| Opus 5.5 | $0.00067 | $0.00873 |
| Sonnet 5.5 | $0.00033 | $0.00437 |
| Haiku 4.5 | $0.00017 | $0.00218 |
Grade A, and why
dataset 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dataset acquisition
Every dataset a project acquires gets TWO artifacts in a task folder under the external data directory. A corpus present without its sidecar is a defect - nobody downstream can tell what it is, where it came from, or whether it may be used.
dataset-<name>.zip- the archive, gitignoreddataset-<name>.md- the sidecar, tracked
Sidecar survives the archive. Archives are large, rebuildable and machine-local; the sidecar is the only record that reaches another machine, another repo, or a reader six months on.
Ask where it goes (MANDATORY - before creating anything)
Propose a location and WAIT for the answer. Not before the first byte is fetched - before the directory is created, because the sidecar is written and tracked before any download happens. Projects differ on where external data lives, and a corpus written to the wrong tree is a large file to move and a gitignore rule to redo.
- Suggest
data/external/<task>-datasets/, naming the task you inferred from the request - Offer the alternatives you can see on disk - an existing
data/external/*sibling, adatasets/root, a path already in.gitignore - Wait for the answer, then reuse the confirmed location for the rest of that task without asking again
Layout
data/external/<task>-datasets/
├── dataset-ragtruth.zip # gitignored
├── dataset-ragtruth.md # tracked
├── dataset-edgar-restricted.md # tracked - describes the tree below, no archive
└── edgar-restricted/ # gitignored
- Task folder, not a flat dump - one folder per task (
grounding-datasets/,ner-datasets/,forecasting-datasets/), so a project running three tasks does not have to reason about which corpus belongs to which - Archive per corpus where the corpus fits an archive; an extracted tree beside the sidecar where it does not (multi-GB, incremental, or fetched file-by-file)
<name>- lowercase-hyphen, matches the spec key, identical across.zipand.md- Scaffolding a project that will hold data → create
data/external/<task>-datasets/with the gitignore rules below before the first fetch
What ships with it
3 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.
- 1mo ago Changed · -4 tokens per session ebfffda47875
- 1mo ago First seen · 122 lines · 171 tokens per session scan A a471941f1fb1
dataset is a skill published in the GitHub repository stellarshenson/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 167 tokens to every session and 2,183 once invoked, about $0.0007 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-31.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…