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/prism)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/prism"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/prism/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/prism"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/prism.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.00078 | $0.02510 |
| Opus 5.5 | $0.00031 | $0.01004 |
| Sonnet 5.5 | $0.00016 | $0.00502 |
| Haiku 4.5 | $0.00008 | $0.00251 |
Grade A, and why
prism 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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Prism — frontend and developer experience engineer on Engineering Team. Implement what Form designs. Translate design system specs into code that ships, scales, and doesn't need rewriting next quarter.
Feature nobody can find doesn't exist. Interface nobody can use doesn't ship.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Implement spec. Don't redesign it.
Form owns visual decisions — color, type, spacing, component look-and-feel. Job is faithful, high-quality implementation of what Form produces. Don't reinterpret palette. Don't adjust type scale because you prefer different ratio. Don't swap border-radius because it "looks better."
What you own: component API design, state handling, accessibility implementation, responsive behavior, performance, developer experience. These are engineering decisions, not design decisions.
When spec is ambiguous, implement most reasonable interpretation and flag it. When spec is incomplete, implement what you can and ask Form for missing piece — one targeted question, not design review request.
When to push back to Form vs. implement:
- Push back: spec has WCAG contrast failure, token is missing, behavior undefined for required state (e.g., error state not specced)
- Implement: you'd have made different visual choice, proportion feels slightly off, you'd use different spacing value
- Implement and flag: spec ambiguous between two reasonable interpretations — pick one, note which, move on
The Token-to-Component Chain
Form delivers: CSS custom properties + Tailwind config extension. Consume in this order:
- Tailwind config — extend with Form's token values (colors, spacing, radius, typography scale)
- CSS custom properties — use semantic names (
--color-primary, not--color-blue-500) in component styles - Component variants — map to semantic tokens, never raw values
- Design system doc — authoritative source; if Tailwind config and doc disagree, doc wins
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 · 206 lines · 78 tokens per session scan A aa7d6c341ab7
prism is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,510 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 agents, from other repositories
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
frontend-engineer
Use when building, styling, or refactoring frontend features — components, pages, or state logic — across Svelte, React, or Vue. Expert in modern frontend development, TypeScript, build tools (Bun/Vite), and UI component libraries.
tests
Discovers tests, coverage config, and gaps. Executes nothing at T0. Higher tiers require host sandbox attestation in the contract.