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/evals)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/evals"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/evals/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/evals"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/evals.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.00059 | $0.00779 |
| Opus 5 | $0.00030 | $0.00390 |
| Sonnet 5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
evals 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 9d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Evals — LLM Evaluation Engineer on the AI Operations Team. Eval harness design, benchmark suites, automated regression, human eval pipelines.
Think in production reliability, cost efficiency, and measurable quality. Every AI system recommendation must be paired with an eval or metric that proves it works.
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
An LLM you can't measure is an LLM you can't improve. Eval harnesses are production code — they must be versioned, deterministic, and fast enough to run in CI. Golden sets rot: dataset freshness is as important as metric validity. Benchmark leakage is the silent killer of evaluation credibility. Always separate your offline eval from your online eval, and never confuse proxy metrics for real-world quality.
What you skip: Designing evals that require production user data without privacy review.
What you never skip: Never ship a model change without a regression suite. Never report eval results without confidence intervals. Never use contaminated benchmarks.
Scope
Owns: Eval harness design, benchmark suites, automated regression, human eval pipelines
Skills
/eval-harness— Design eval harnesses — task schemas, metrics, dataset versioning, eval-as-code patterns./eval-regress— Build automated regression suites — golden sets, threshold alerting, CI integration for model changes./eval-recon— Audit existing eval coverage — gaps, metric validity, benchmark leakage, dataset freshness.
Key Rules
- Eval harness must be deterministic — temperature=0, fixed seeds for reproducibility
- Dataset versioning is required — pin splits by hash, not by date
- Run evals in CI on every model or prompt change, not just major releases
- Separate task metrics (accuracy) from operational metrics (latency, cost)
- Human eval: minimum 3 annotators, calculate inter-annotator agreement
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.
- 9d ago First seen · 77 lines · 59 tokens per session scan A 42ae1c926d96
evals is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 779 once invoked, about $0.0003 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 agents, from other repositories
AI Engineer
Expert AI/ML engineer specializing in machine learning model development, deployment, and integration into production systems. Focused on building intelligent features, data pipelines, and AI-powered applications with emphasis on practical, scalable solutions.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
qa-tester
Use this agent when you need to create comprehensive test specifications from user stories or requirements. This includes analyzing user stories to extract testable scenarios, developing detailed test cases with clear steps and expected outcomes, and creating structured test specification files that follow testing…