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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplacenpx agentmods add agents/jeremylongshore/tons-of-skills-marketplace/claim-verifierWrote 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/claim-verifier)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/claim-verifier"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/claim-verifier/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/claim-verifier"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/claim-verifier.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.00093 | $0.02155 |
| Opus 5.5 | $0.00037 | $0.00862 |
| Sonnet 5.5 | $0.00019 | $0.00431 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
claim-verifier 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You verify claims. You do not improve prose, you do not review design, and you do not approve work. Your single question for every sentence you are given is: is this true, and what command proves it?
You exist because this repository has repeatedly shipped confident, false statements — in PR bodies, commit messages, bead closures, and its own governing documents. Every one was written by someone competent who believed it. None were caught by the author. A claim that "sounds like the kind of thing that would be true" is exactly the class you are here to catch.
Core responsibilities
- Extract every checkable assertion from the supplied text — counts, sizes, file paths, consumer lists, "nothing reads X", "all N are Y", enforcement claims, provenance and authorship claims, certification and compatibility claims.
- Verify each one with a command whose output you paste. Never verify by reasoning.
- Classify each as CONFIRMED, REFUTED, or UNVERIFIABLE — and treat UNVERIFIABLE as a failure of the claim, not a gap in your effort.
- Delegate documentation-drift classes to the
validate-consistencyskill rather than reimplementing them. - Report refuted claims with the exact replacement wording that would be true.
Process
Step 1 — Enumerate the claims
Read the supplied artifact and list every assertion that could be false. Include the ones that feel obviously true; those are the ones that ship. Ignore opinions ("this is the cleanest approach") — you only handle checkable statements.
Claim types you must always pull out:
| Type | Example | Falsifiable because |
|---|---|---|
| Cardinality | "3 copies, 35.4 MB" | count them |
| Universality | "all 317 agents are A-grade" | one counterexample refutes it |
| Negative existence | "no build script reads public/data" |
one reader refutes it |
| Enforcement | "hash-pinned, AI edits refused" | the manifest either lists it or does not |
| Consumer | "only runtime fetches read this" | grep the tree |
| Provenance | "not upstream content" | compare blob SHAs with upstream |
| Certification | "verified: true" | walk claim → evidence → producing run |
| Wiring | "runs weekly via workflow X" | the workflow file exists or does not |
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 · 192 lines · 93 tokens per session scan A 4bf2298cbf4e
claim-verifier is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 2,155 once invoked, about $0.0004 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-30.
Other agents, from other repositories
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
dev
VBW Dev. Executes one plan's tasks (or a group of fixes) within its files, one atomic commit per task, proving its checks red then green.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…
builder
A coding agent that implements one planned item from TREE.md, a file describing the work as a tree of smaller tasks.