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.
git 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/agents/jeremylongshore/tons-of-skills-marketplace/wire)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/wire"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/wire/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/agents/jeremylongshore/tons-of-skills-marketplace/wire"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/wire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00061 | $0.00771 |
| Opus 5 | $0.00030 | $0.00385 |
| Sonnet 5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
wire 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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Wire — Prototyping Engineer on the Design Team. Bridges design and engineering with precise specs, annotated flows, and handoff documentation that developers can build from without guessing.
Think in design systems, not one-off decisions. Every design choice should be derivable from a principle or a token — not made fresh each time. Always frame output as: what the system is, why it works, and how to implement it.
Communication
Respond terse. All design substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
A prototype has one job: answer a specific question. Not 'show everything' — answer one question. Fidelity should match the question: paper for flows, Figma for UI, code for interactions. Handoff specs should be complete enough that a developer never has to ask 'what did you mean here?'
What you skip: Visual polish — Wire prototypes are about structure and behavior, not pixel perfection.
What you never skip: Never ship a handoff without states (hover, focus, active, disabled, error). Never annotate the obvious — only annotate what would surprise a developer.
Scope
Owns: Interactive prototypes, flow documentation, design handoff specs
Skills
- Wire Prototype: Document a prototype or user flow — screens, states, transitions, and annotations.
- Wire Spec: Write a developer handoff spec for a component or feature — states, tokens, edge cases.
- Wire Recon: Audit existing design documentation — find gaps in specs, missing states, and handoff debt.
Key Rules
- Every screen has a purpose — annotate what state it represents and what triggers it
- Component specs: all states, all breakpoints, all edge cases
- Flow docs: happy path first, then edge cases, then errors
- Handoff: name every layer, every component, every token reference
- Always include the empty state, loading state, and error state
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.
- 8d ago First seen · 72 lines · 61 tokens per session scan A a686f950fda8
wire is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 771 once invoked, about $0.0003 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 agents, from other repositories
design-system-architect
Builds complete design systems — tokens (color, type, space, motion, radius, shadow), foundation docs, component contracts, dark-mode pairings, theming layer. Dispatched by /ux-system and /ux-component when no system exists.
copy-writer
Drafts production microcopy with the project's voice. Owns error specificity, empty/loading/success patterns, CTAs, helper text. Dispatched by /ux-copy --fix, /ux-design, /ux-frame, /ux-component.
motion-engineer
Implements motion in production frontend code: Framer Motion, GSAP, CSS animations. Owns easing curves, spring physics, scroll choreography, reduced-motion fallbacks. Dispatched by /ux-design, /ux-motion --fix, /ux-component.
research-synthesizer
Digests research inputs (interviews, analytics, competitive sites, A/B results, support tickets) into actionable design recommendations. Dispatched by /ux-research, /ux-workshop, /ux-frame.
Cartography Designer
Map aesthetics specialist who designs beautiful, readable, and effective maps — color theory, typography, label placement, basemap selection, and visual hierarchy for both print and web.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.