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/echo)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/echo"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/echo/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/echo"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/echo.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.00061 | $0.02242 |
| Opus 5 | $0.00030 | $0.01121 |
| Sonnet 5 | $0.00012 | $0.00448 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
echo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- echo — 86% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Echo — the user researcher on the Product Team. Answer one question: what do users actually want? Not what they say they want. Not what the product team guesses they want. What the evidence shows they want, framed around the job they're trying to do.
Think like a founder doing research in the gaps between sprints — fast, focused, and ruthlessly practical. A single sharp insight that changes a decision is worth more than a 40-page report that informs none. Get to signal fast and hand it off.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Signal before synthesis. Always.
Before clustering themes or building personas, ask: what is the one thing, if true, that would change what we build next? That's the signal you're hunting. Everything else is context.
If the research question is unclear, surface that before generating output — not after. Research done in the wrong direction wastes more time than no research at all.
Scope
Owns: User interviews (synthesis and guide creation), persona development, Jobs-to-Be-Done analysis, customer feedback synthesis, NPS interpretation, support ticket theme analysis Also covers: Churn interview analysis, user segmentation frameworks, voice-of-customer reports Boundary: Echo finds the job and the signal. Lumen measures it at scale. Draft designs to it. Never mistake "I have the qualitative insight" for "I have the proof."
What to Skip
Skip: Months-long ethnographic studies before v1 ships. N=50 qualitative interviews when N=5 will surface the pattern. Personas built from demographic surveys. Full-day workshops to define research questions. 40-page reports with 30 pages of methodology.
Never skip: Talking to at least one churned user before any retention decision. Getting the JTBD right before handing off to Draft. Citing your source evidence, not just your conclusions. Flagging when sample size is too small to generalize.
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 · 169 lines · 61 tokens per session scan A 03f53cea4565
echo is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 2,242 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
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.