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 designgit 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/design)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/design"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/design/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/design"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 140 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00126 | $0.01970 |
| Opus 5 | $0.00063 | $0.00985 |
| Sonnet 5 | $0.00025 | $0.00394 |
| Haiku 4.5 | $0.00013 | $0.00197 |
Grade A, and why
design 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design
Systematic, anti-slop product design. All agents inherit the session model. Reviewers bold-labeled; Workers plain.
This skill exercises Layer 4 (Brainstorming/Spec) and the design layer of Layer 0 (Project Analysis). It is
thinking, not building — no source code is written here. The only writes are to .hyperflow/design/system.md and
.hyperflow/specs/. It ends with a handoff gate into /hyperflow:plan → /hyperflow:dispatch for the build.
Iron Rules
- Design system first. Every run establishes or extends
.hyperflow/design/system.mdbefore designing a screen, per../hyperflow/design-system.md. The system is created once and extended, never regenerated. - Researched, not invented. Ground every direction in ≥2 real products from the project's field, combine
them, then diverge with one deliberate signature (the method in
design-system.md). - Local taste skills are invoked live. The main session calls
Skillto invoke the matching taste skill; the dispatcheddesigneragent Reads theSKILL.mdand applies it (it has noSkilltool). - Per-step agents (DOCTRINE rule 12). No inline design — the
designerspecialist does the work; anaccessibility-reviewerpass gates the result. - No code in the design phase. Design produces a system file and a design spec;
dispatchexecutes them. - Failure recovery (DOCTRINE rule 14) per
../hyperflow/failure-recovery.md. - No AI attribution in any file written.
Per-Step Agent Map (DOCTRINE rule 12)
| Step | Sub-phase | Workers | Reviewers | Notes |
|---|---|---|---|---|
| 1 — Triage | — | — | — | Mechanical classification (exempt) per ../hyperflow/task-triage.md |
| 2 — Design system | 2a — establish/extend .hyperflow/design/system.md |
designer |
Reviewer | Creates if missing; extends if present |
| 3 — Research + direction | 3a — prior-art research + combine + diverge | designer (fan-out ≤ 3 by dimension) |
Reviewer | Web-research-first; ≥2 references |
| 4 — Design spec | 4a — translate direction into tokens/spec | designer |
Reviewer | Written to .hyperflow/specs/<slug>.md |
| 5 — Taste + a11y review | — | — | designer verdict + accessibility-reviewer |
Anti-slop floor + WCAG floor |
| 6 — Handoff gate | — | — | — | AskUserQuestion only (exempt — structural gate) |
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 · 142 lines · 126 tokens per session scan A 0630166fdc5f
design is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,970 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
suanfish-design-system
A Chinese design system for creating and reviewing web interfaces, with multiple design perspectives working together. It focuses on React and Tailwind-based projects.
extract-design-system
Extract design primitives from a public website and generate starter token files for your project.
ui-design
A structured approach to designing user interfaces—the screens and controls people use in software—before writing the frontend code.
awesome-design-md
Create a DESIGN.md style baseline BEFORE building UI. Use FIRST when no design draft exists — installs a proven visual style, then invoke frontend-design to implement. For borrowing a known product style, getting consistent typography/colors/spacing, or needing a fast visual starting point.
hatch3r-design-system-detect
Detects existing design tokens, component library, and theming convention in a project before authoring new UI primitives — output a concise inventory for downstream implementers.
anti-slop-frontend
Use when anti-slop frontend framework for AI agents. Enforces better layout, typography, motion, and spacing to counter generic AI-generated boilerplate UIs. Use when building frontend, countering generic AI UIs, need distinctive visual design, image-to-code pipeline.