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.
npx skills add jeremylongshore/tons-of-skills-marketplace --skill issuegit 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/skills/jeremylongshore/tons-of-skills-marketplace/issue)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/issue"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/issue/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/skills/jeremylongshore/tons-of-skills-marketplace/issue"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00115 | $0.01802 |
| Opus 5 | $0.00057 | $0.00901 |
| Sonnet 5 | $0.00023 | $0.00360 |
| Haiku 4.5 | $0.00012 | $0.00180 |
Grade A, and why
issue 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 13d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue
GitHub-native entry point for the chain: one issue URL in, one reviewed pull request out. This skill owns
ingestion, triage, and spec synthesis; everything after that is the standard chain (/hyperflow:plan →
/hyperflow:dispatch) with GitHub chain args propagated so dispatch's Step 5 offers the PR exit. The
maintainer-side counterpart is /hyperflow:pr (review an incoming PR).
Step 0 — Preflight
- Resolve the argument: full URL,
#N, or bare number against the current repo'sorigin. No GitHub remote → stop withNo GitHub remote — /hyperflow:issue needs a repo with an origin on GitHub. gh auth status(once per chain). Unauthenticated → continue in local-only mode: the chain still runs, the PR exit and any comment posting are skipped, and the wrap-up prints the exactgh auth login+gh pr createcommands to finish by hand. Never half-post.gh issue view <n> --json title,body,comments,labels,author,state,url. Closed issue → confirm intent viaAskUserQuestion(Work on it anyway / Stop— binary, no marker).
Step 1 — Triage (decision agent)
Dispatch a triage consultation per ../hyperflow/task-triage.md over the full
thread (body + comments + labels). Classify:
| Class | Route |
|---|---|
| Bug report | Root-cause discipline from ../trace/SKILL.md — reproduce before any patch; then the fix chain on fix/issue-<n>-<slug> |
| Feature / enhancement | /hyperflow:plan chain on feat/issue-<n>-<slug> |
| Question / discussion | Draft a reply, show it, and offer to post (gated by comment=). Never a code chain. |
| Invalid / spam / already fixed | Report the finding + draft a closing reply (gated). Stop. |
Already-solved check (mandatory): before planning any work, the triage agent verifies against current main
whether the ask is already satisfied — issues are often filed against stale versions. Partially-satisfied →
the spec scopes only the remaining delta and says so.
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.
- 13d ago First seen · 114 lines · 115 tokens per session scan A 0f7fea844d69
issue is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 1,802 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.
fix
Use when the user provides a GitHub Issue URL and wants it fixed in the current repo. Do NOT use for feature requests without a clear bug or for PRs (use /code-review).
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.
mk:respond-pr
Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread. Use when responding to received PR feedback. NOT for giving a review (see mk:review-pr); NOT for implementing the fixes (hand off to mk:fix).
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…