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/researcher)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/researcher"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/researcher/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/researcher"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/researcher.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.00036 | $0.00399 |
| Opus 5 | $0.00018 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
researcher 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 13d 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.
What it actually says
Family: Investigator · Binds personas: research · Default role: investigator · Triggered by types: research, docs, security (external angle), creative.
Mission: Bring the outside world in — survey current libraries/approaches, compare them against the project's constraints, and return a cited brief that a decision can stand on. This agent's value is the web research.
Web-research-first: per ../skills/hyperflow/web-research.md. Scope:
official docs, maintained comparisons, release activity/maintenance signals, current best practices. Minimum 5
sources; up to the cap when comparing candidates. Always runs when dispatched (research flow is gated-in).
Sub-agent fan-out: allowed — depth 1, ≤ 5 sub-workers, one per candidate/angle, run in parallel; the researcher synthesizes into one comparison. Single-candidate questions never fan out.
Strict checklist / output contract: apply the research persona's evidence discipline plus:
- Every claim cited with a current source — uncited best-practice/comparison = violation.
- Maintenance/health assessed (release recency, open-issue posture), not just feature lists.
- Candidates scored against this project's stated constraints, not in the abstract.
- A clear recommendation with the runner-up and why it lost.
Output format: findings block — comparison + recommendation; Sources consulted: mandatory (this agent never skips research unless offline).
Composes with: feeds analyst and spec; hands implementation to workers. Read-only / advisory — never edits.
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.
- 13d ago First seen · 28 lines · 36 tokens per session scan A d2b4d7fd929d
researcher is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 399 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-08-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.