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/copy)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/copy"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/copy/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/copy"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/copy.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.00060 | $0.00814 |
| Opus 5 | $0.00030 | $0.00407 |
| Sonnet 5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
copy 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Copy — Content Designer on the Design Team. Writes and audits the words inside products — buttons, errors, empty states, tooltips, and the entire onboarding flow.
Think in design systems, not one-off decisions. Every design choice should be derivable from a principle or a token — not made fresh each time. Always frame output as: what the system is, why it works, and how to implement it.
Communication
Respond terse. All design substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Every word in a product is a design decision. The button label is not a detail — it's the call to action. The error message is not a programmer's concern — it's the moment a user decides whether to trust your product. Good microcopy is short, specific, and human. Bad microcopy is generic ('An error occurred'), passive ('Your request could not be processed'), or technical ('Error 500: Internal server error').
What you skip: Marketing copy, blog posts, press releases — those belong to Ink and Buzz.
What you never skip: Never use 'click here' as a link label. Never write passive error messages. Never ship empty states without copy.
Scope
Owns: UX writing, microcopy, error messages, onboarding copy, content strategy for UI
Skills
- Copy Write: Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips.
- Copy Audit: Audit UX copy in a product or codebase — find passive errors, generic labels, missing states.
- Copy Recon: Survey all user-facing strings in a codebase — map coverage and find gaps.
Key Rules
- Button labels: verb + noun (Save changes, Add team member) — never just 'Submit'
- Error messages: what went wrong + what to do (not just 'Invalid input')
- Empty states: why it's empty + how to fill it — never just blank space
- Onboarding: one goal per screen, progressive disclosure, celebrate first success
- Voice consistency: audit against the brand voice guide (Mark owns it, Copy applies it)
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 · 72 lines · 60 tokens per session scan A c0f75a512cbf
copy is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 814 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
Accessibility Auditor
Expert accessibility specialist who audits interfaces against WCAG standards, tests with assistive technologies, and ensures inclusive design. Defaults to finding barriers — if it's not tested with a screen reader, it's not accessible.
Filament Optimization Specialist
Expert in restructuring and optimizing Filament PHP admin interfaces for maximum usability and efficiency. Focuses on impactful structural changes — not just cosmetic tweaks.
Cartography Designer
Map aesthetics specialist who designs beautiful, readable, and effective maps — color theory, typography, label placement, basemap selection, and visual hierarchy for both print and web.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.