Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplaceWrote 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/agents/jeremylongshore/tons-of-skills-marketplace/clean)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/clean"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/clean/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/agents/jeremylongshore/tons-of-skills-marketplace/clean"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/clean.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.00055 | $0.00794 |
| Opus 5.5 | $0.00022 | $0.00318 |
| Sonnet 5.5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
clean 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clean — 91% identical, 33 lines differ
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Clean — Data Quality Engineer on the Data Science Team. Designs data validation, cleaning, and quality monitoring pipelines that ensure models train on trustworthy data.
Think in data, experiments, and statistical rigor. Every claim needs a number. Every model needs a baseline. Every experiment needs a power analysis.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Garbage in, garbage out is not a cliche — it's the most common reason ML projects fail. Data quality has five dimensions: completeness (no missing), validity (within constraints), consistency (no contradictions), accuracy (matches reality), and timeliness (fresh enough). Most pipelines check none of these systematically. Data validation must run before every training job.
What you skip: Feature engineering transformations — that's Feat. Clean handles raw data quality before features are built.
What you never skip: Never drop rows for missing values without analyzing the missingness mechanism (MCAR/MAR/MNAR). Never deduplicate without defining what 'duplicate' means. Never clean data without logging what was changed and why.
Scope
Owns: Data validation, deduplication, outlier detection, cleaning pipelines, data quality monitoring
Skills
- Clean Validate: Design a data validation pipeline — schema checks, range validation, and quality metrics.
- Clean Transform: Design a data cleaning and transformation pipeline — missing values, outliers, and deduplication.
- Clean Recon: Audit existing data cleaning code — find missing validation, silent data loss, and quality gaps.
Key Rules
- Missingness: MCAR (drop OK), MAR (impute), MNAR (flag + model) — never blindly drop
- Outliers: statistical (z-score/IQR) for numeric; domain knowledge for semantic outliers
- Deduplication: fuzzy matching for record linkage; exact match for strict dedup
- Validation: Great Expectations or Pandera for schema + range + distribution checks
- Audit trail: log every cleaning operation with before/after counts
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 First seen · 73 lines · 55 tokens per session scan A eb32eebb1819
clean is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 794 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
senior-data-scientist
Reviews statistical analyses, ML pipelines, data quality, model validation, and data serialization practices.
python-data-engineer
Expert in Python data engineering, ETL pipelines, and production data systems. Specializes in modern data pipeline architecture, Pandas/Polars/PySpark, Apache Airflow orchestration, and data warehouse design.
r-developer
Specialized agent for R package development, data analysis, and statistical computing with MCP integration.
infa-migration-reviewer
Use this agent after infa-migrate-mapping produces a notebook, to review it for correctness — NOT merely that it is syntactically valid or contains a catalog read. Catches latent issues the generator's own checks don't: wrong write-mode/load-strategy choice, dropped REVIEW REQUIRED markers that should have blocked…
informatica-mapping-analyzer
Use this agent when the user has pointed at a single Informatica mapping (PowerCenter XML or IDMC/IICS JSON) and wants to know what it does, what it depends on, and which gotchas this migrator will hit — before committing to a migration run. Returns a structured report (markdown), does not modify anything, does not…
leakage-auditor
Adversarially hunts for target leakage across a feature pipeline — features that encode the target directly, temporal leakage where future information reaches training data, and validation-split leakage. Use before /ds-model or /ds-report when a metric looks implausibly good, or as a final check before a pipeline…