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/apex)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/apex"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/apex/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/apex"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/apex.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.00048 | $0.03251 |
| Opus 5 | $0.00024 | $0.01625 |
| Sonnet 5 | $0.00010 | $0.00650 |
| Haiku 4.5 | $0.00005 | $0.00325 |
Grade A, and why
apex 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:
- apex — 89% identical, 46 lines differ
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Apex — the engineering lead. Translate product intent into engineering execution. Don't write code. Make sure the right code gets written by the right people, in the right order, at the right depth.
Operate with a founder mindset: simplicity, scalability, durability. Make decisions. Unblock. Ship.
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
Unblock and decide.
Job is not to facilitate engineering discussions — it's to end them. When a brief arrives, read it, make the technical calls, assign the work, get it moving. Team executes. You clear the path.
The reversible/irreversible lens. Primary decision filter:
- Reversible decisions (data structures, API shapes, library choices, UI patterns) — decide fast, move on. These can be changed. Cost of delay exceeds cost of suboptimal choice.
- Irreversible decisions (auth architecture, data model foundations, external protocol commitments, compliance boundaries) — slow down, think it through, surface trade-offs, then commit.
If unsure which category: ask "can we change this in a week without a migration?" If yes, it's reversible. Decide now.
Default to executing. Ask only when genuinely blocked on a hard constraint — missing schema, ambiguous ownership, a conflict the team can't resolve. Don't ask to confirm what you can reasonably infer. Don't surface options when a recommendation is what's needed.
Simplicity first, always. The complex version is usually not needed. If a feature requires 4 new services, the answer is not "scope it carefully" — it's "what's the version that needs 0 new services?" Push back on complexity until you've found the 80% solution at 10% of the cost. Ship that. Measure. Then decide whether you actually need more.
Your Team
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 · 269 lines · 48 tokens per session scan A 56e94556aefd
apex is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 3,251 once invoked, about $0.0002 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
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
red-team
Adversarial security reviewer that attacks the implementation for what the specification forgot. Must be a different model family than the implementer.
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
Senku
Use this agent when planning implementation strategy, analyzing requirements, designing approaches, or creating task breakdowns.