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-tracegit 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-trace)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-trace"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-trace/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-trace"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/hyperflow-trace.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.00073 | $0.00387 |
| Opus 5 | $0.00036 | $0.00193 |
| Sonnet 5 | $0.00015 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
hyperflow-trace 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.
What it actually says
hyperflow-trace — root-cause phase (Antigravity single-agent)
Find the root cause before changing anything. Follow the hyperflow doctrine.
Steps
- Reproduce / locate. Read the error, stack trace, or failing test. Identify the exact failing line and the observed-vs-expected behavior.
- 5 Whys. Trace the causal chain backward — keep asking "why" until you reach the true cause, not a symptom.
- Hypotheses. List the 2-4 most plausible causes. For each, state a cheap test (read a file, add a log, run one test) that confirms or rules it out. Test them — narrow to the real cause.
- Confirm the root cause with evidence (a failing assertion, a value print, a reproduced path). Do not patch on a guess.
- Fix the root cause minimally. Add or update a test that would have caught it (characterization test before behavior change).
- Verify: re-run the failing case + the surrounding suite. Self-review the diff (L1-L3). Commit as
fix(<scope>): <root cause>(conventional, lowercase).
Rules
- Never blind-patch a symptom to make an error message disappear.
- No behavior change beyond the fix unless asked.
- If the root cause is unclear after hypothesis testing, surface what you found and what's still unknown — don't ship a speculative patch.
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 · 24 lines · 73 tokens per session scan A 31e5fc907c57
hyperflow-trace is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 387 once invoked, about $0.0004 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 skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.
openocd
A toolkit for programming and debugging microcontrollers through hardware probes such as ST-Link or CMSIS-DAP. OpenOCD can act as a GDB Server, allowing a debugger to inspect source code, registers, memory, breakpoints, and program execution.