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.5 | $0.00029 | $0.00155 |
| Sonnet 5.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 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.
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.
- 1mo 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,881 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 387 once invoked, about $0.0003 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.