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 hyperflow-plangit 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/hyperflow-plan)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-plan"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-plan/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/hyperflow-plan"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-plan.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.00124 | $0.00623 |
| Opus 5.5 | $0.00050 | $0.00249 |
| Sonnet 5.5 | $0.00025 | $0.00125 |
| Haiku 4.5 | $0.00012 | $0.00062 |
Grade A, and why
hyperflow-plan 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hyperflow-plan — planning phase (Antigravity single-agent)
Thinking, not building. The only writes are to .hyperflow/. Each phase skips itself when the request doesn't need it. Follow the hyperflow doctrine (autonomy, file-first, AskUserQuestion gates).
Steps
- Amplify (skippable). If the prompt is rough, rewrite it into its strongest form — role · task · context · constraints · output spec. Skip when it's already specific. Never inflate a one-line ask into a spec.
- Research first. Read the relevant code,
AGENTS.md, and.hyperflow/memory/*. Map the affected surface yourself — do not ask what the code answers. - Design (skippable). For an open-ended request: ask ≥2 clarifying questions (what/which/where only), propose 2–3 approaches, then design section-by-section into
.hyperflow/specs/<slug>.mdwith approval per section. A clear request bounces straight to decomposition. When a system, UI, motion, or mobile surface is in scope, ground the design in the matching standards (architecture decomposition + a diagram, the design system, the Motion language, the mobile platform/device matrix). - Decompose. Produce a topologically-ordered batch graph; each sub-task = one conventional-commit-sized change. Split any sub-task touching >5 files, >500 LOC, 2+ subsystems, or >10-min review. Write
.hyperflow/tasks/<slug>.md: status table → Goal → Why → Scope-at-a-glance → Affected files → Execution plan → Batches (role, files, complexity, acceptance criteria, commit stub) → Verification plan. - Print
Plan ready — .hyperflow/tasks/<slug>.md (N batches, M sub-tasks). - Hand off: invoke the
hyperflow-dispatchskill with the task slug — or, in two-session mode, write a committed handoff package and stop.
Rules
- No implementation code; no source edits.
- Floor of 2 clarifying questions on the design path; 0–3 on the bounce (decompose-only) path.
- Single-batch plans for multi-file work are an anti-pattern — decompose.
- Always include a concrete verification plan.
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 · 25 lines · 124 tokens per session scan A 2793870e8631
hyperflow-plan is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,881 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 623 once invoked, about $0.0005 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…