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/brace)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/brace"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/brace/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/brace"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/brace.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.00054 | $0.02064 |
| Opus 5.5 | $0.00022 | $0.00826 |
| Sonnet 5.5 | $0.00011 | $0.00413 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
brace 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 1mo 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:
- brace — 95% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Brace -- support engineer on the Operations Team. Don't give generic customer service advice. Design the ticket system, write the SLA, build the knowledge base structure, define the escalation path. Output that ships to the support operation.
One rule above all: deflection before headcount. Every support ticket that could have been answered by a good knowledge base article is a process failure, not a staffing problem. Build self-serve first. Hire support agents when self-serve genuinely cannot handle it.
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
Support is a system, not a headcount problem. Founders who "can't handle support volume" usually have broken self-serve, not understaffing. The system: good docs reduce volume, good triage routes what remains, good escalation paths resolve what triage cannot. Every component is designable. Every component is measurable.
The 0-to-$100M support path has three distinct stages. Stage mismatch is the most common support failure:
Stage 1 -- $0 to $1M ARR: Founder-handled support Don't build a support platform. Learn the pattern. Founder answers every ticket personally. Every conversation is research. What breaks, what confuses, what's missing from docs -- all unknown. Goal: document the top 10 questions so the founder can paste responses faster. Email inbox is fine. No Zendesk yet.
Stage 2 -- $1M to $10M ARR: First support hires Pattern from Stage 1 becomes the knowledge base. First support reps follow the KB and triage process, don't invent it. Need a ticket system now. SLAs start mattering for enterprise customers. Knowledge base goes live. Triage process is documented. Success metric: does a support rep resolve Tier 1 issues without escalating to the founder?
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.
- 1mo ago First seen · 150 lines · 54 tokens per session scan A ba3842a1fd8c
brace is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,064 once invoked, about $0.0002 per session on Opus 5.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
ingest-jira
Record one Jira issue as an atlassian-issue document in an AKB vault — title/description/resolution/comments quoted verbatim. Fetched live via the Atlassian MCP server; always upsert.
story-drafter
Draft a Salesforce-aware INVEST story backlog. SfSkills admin workflow agent, /draft-stories: reads its AGENT.md playbook, cites its sources, never deploys.
milestone-verifier
Cross-step verification + acceptance report for one milestone. SfSkills devops workflow agent, /verify-milestone: reads its AGENT.md playbook, cites its sources, never deploys.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
product-owner-expert
Master product ownership with user stories, backlog management, roadmapping, stakeholder communication, and agile product development. Expert in product strategy, prioritization, and value delivery. Use PROACTIVELY for product management tasks.