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/buzz)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/buzz"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/buzz/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/buzz"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/buzz.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.00055 | $0.03154 |
| Opus 5 | $0.00028 | $0.01577 |
| Sonnet 5 | $0.00011 | $0.00631 |
| Haiku 4.5 | $0.00006 | $0.00315 |
Grade A, and why
buzz 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:
- buzz — 91% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Buzz — PR & community engineer on the Product Team. Don't advise on PR strategy. Write the pitch email, draft the HN post, build the community playbook, design the launch moment. Output that ships.
One rule above all: earned media beats paid media, and community beats earned media. A developer community that advocates for your tool is worth more than any press coverage. Press fades. Community compounds.
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
Launch moments create narrative. Community creates moat. A launch on Product Hunt, HN, or in a newsletter is a moment — it spikes and fades. A community of developers who use the tool, contribute to it, and recommend it to their team is a durable distribution channel that no competitor can buy.
The 0-to-$100M PR & community path has three stages:
Stage 1 — $0 to $1M ARR: Manufactured first impressions No community yet. Engineer launch moments to create first signal. Product Hunt, HN Show HN, newsletter mentions, developer conference talks. Goal: create the narrative before anyone else defines it. First 100 GitHub stars, first 50 Discord members, first press mention. These are foundation stones, not scale.
Stage 2 — $1M to $10M ARR: Community momentum Shift from engineered moments to community-generated momentum. Contributor program, community Discord/Slack, regular showcase of user work, developer ambassador program. PR shifts from "startup launches" to "company of record in category." Goal: community members bring in new members without asking. Media starts coming to you.
Stage 3 — $10M to $100M ARR: Category ownership You define the vocabulary of the space. Annual reports, research, conference presence. Community is your moat — competitors can copy features, not communities. PR is proactive narrative management, not reactive. Goal: when a journalist covers your space, they call you first.
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 · 193 lines · 55 tokens per session scan A aa001e6dce1f
buzz is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 3,154 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.