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 statusgit 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/status)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/status"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/status/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/status"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 141 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00072 | $0.03411 |
| Opus 5 | $0.00036 | $0.01706 |
| Sonnet 5 | $0.00014 | $0.00682 |
| Haiku 4.5 | $0.00007 | $0.00341 |
Grade A, and why
status 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Read-only snapshot of the current hyperflow project, with live progress on every active task file. Standalone — does not auto-chain and is never invoked by other skills. Invoked manually via /hyperflow:status.
The skill has two sections:
- Static snapshot — version, profile freshness, memory count
- In-flight work — per-task live progress (sub-tasks done/total, tokens, wall-clock, ETA)
What to read
Static snapshot
| Field | Source | Fallback |
|---|---|---|
| Version | Latest git tag matching v* + tag commit date |
(missing) |
| Profile | .hyperflow/profile.md file modification time |
(missing) |
| Memory | Line count of .hyperflow/memory/index.md minus header rows |
(none) |
| Active tasks | Files matching .hyperflow/tasks/*.md |
(none) |
| Active features | Folders matching .hyperflow/features/*/feature.md |
(none) |
Active features (multi-phase work)
For every .hyperflow/features/*/feature.md (see feature-phases.md), parse its
## Status block and the phase roster, then for each phase-<n>-*/phase.md show the phase status + Progress bar:
── Feature: checkout-redesign ── (2 / 3 phases)
✓ phase-1-data-layer completed
▸ phase-2-api in_progress ████░░░░ 2/5 tasks · running: T3-handlers
phase-3-ui pending depends on phase-2
The per-phase bar uses the same parsing as the per-task-file section below (each phase.md carries the same
## Status block shape). Omit this section when no .hyperflow/features/*/ exist.
In-flight work (per task file)
For every .hyperflow/tasks/*.md, parse its ## Status block (written by /hyperflow:plan at creation and updated by /hyperflow:dispatch after each sub-task PASS — see plan/SKILL.md Step 10):
| Field | Source | Behaviour |
|---|---|---|
| Slug | basename of the task file minus .md |
always present |
| Done / total | Sub-tasks: <done> / <total> from Status block |
falls back to counting [x] vs [x]+[ ] checkboxes if Status missing |
| Done sub-task names | lines with [x] from the ## Batches section |
listed under the bar |
| Running sub-task | the first [~] checkbox (dispatch marks ~ while a sub-task is mid-flight) |
(idle) if none |
| Pending sub-task count | count of [ ] checkboxes |
shown as N pending |
| Tokens used | Tokens used: line from Status block |
(not tracked yet) if Status absent |
| Wall-clock | Wall-clock: line from Status block |
(not started) if no Started: |
| ETA | ETA: line from Status block |
(computing) if <3 sub-tasks done |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 312 lines · 72 tokens per session scan A 9681067bdd33
status is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 3,411 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-08-30.
Other skills, from other repositories
agent-dreaming-agnostic
Memory-agnostic background consolidation — reviews sessions, scores candidates, promotes durable insights to the active memory backend (built-in MEMORY.md or Holographic). Three-phase (Light/Deep/Condensation/REM). Run via cron or manually.
agent-dreaming
DEPRECATED — use agent-dreaming-agnostic instead. Background memory consolidation for built-in MEMORY.md only.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
notes
Skill "notes" from Pinvou/pinvou-agent, covering ima notes, operations, write rules, examples and response handling.
exploiting-format-string-vulnerabilities
Methodology for exploiting format string bugs where attacker-controlled data reaches the format argument of printf-family functions, enabling stack/memory disclosure (info leaks for ASLR/PIE/canary defeat) and arbitrary write primitives (%n) to hijack control flow via GOT/.finiarray overwrites.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.