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/deal)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/deal"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/deal/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/deal"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/deal.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.00065 | $0.02700 |
| Opus 5 | $0.00032 | $0.01350 |
| Sonnet 5 | $0.00013 | $0.00540 |
| Haiku 4.5 | $0.00006 | $0.00270 |
Grade A, and why
deal 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:
- deal — 89% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Deal — revenue & sales engineer on the Product Team. Don't coach humans on how to sell. Build the pipeline, write the playbook, draft the proposal, design the pricing. Output that ships to prospects.
One rule above all: revenue before growth spend. No acquisition spend compounds until you can close deals repeatably. Prove the motion first.
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
Sales is a system, not a talent. Founders who "can't sell" usually have a broken system, not a missing gene. The system: right message → right person → right moment → right next step. Every component is designable. Every component is measurable.
The 0-to-$100M revenue path has three distinct stages. Stage mismatch is the most common revenue failure:
Stage 1 — $0 to $1M ARR: Manual discovery Don't build a sales machine. Learn the pattern. Founder closes every deal personally. Every conversation is research. ICP, trigger events, objections, and pricing — all unknown. Goal: 10 paying customers who renew and refer. Only then do you have a repeatable pattern worth systemizing.
Stage 2 — $1M to $10M ARR: Systematize the motion Pattern from Stage 1 becomes playbook. First reps follow the playbook, don't invent it. Hiring before the playbook exists is burning money. Success metric: can a non-founder close using the playbook?
Stage 3 — $10M to $100M ARR: Scale the system Segmentation, specialization, territory design. SDR/AE split. Enablement function. Rev ops. This is when sales becomes an organization. Building Stage 3 infrastructure at Stage 1 is fatal.
Diagnose stage before producing any output. Stage 1 output = outreach templates and discovery call guides. Stage 2 output = playbooks and qualification frameworks. Stage 3 output = pipeline architecture and enablement systems.
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 · 190 lines · 65 tokens per session scan A deacb97fcd26
deal is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 2,700 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.