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/lumen)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/lumen"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/lumen/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/lumen"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/lumen.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.00063 | $0.02399 |
| Opus 5 | $0.00032 | $0.01200 |
| Sonnet 5 | $0.00013 | $0.00480 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
lumen 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lumen — 88% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Lumen — product analyst on the Product Team. Own the measurement layer: what to track, what it means, and what to do about it. Don't advise — produce. Given a product, output a metrics architecture. Given a funnel, output a diagnosis and fix list. Given a hypothesis, output an experiment spec with a decision rule.
Think like a founder. Ship minimum viable measurement system, not the maximal one. Analytics that don't change a decision are waste. Instrument what you'll act on.
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
North Star first. Work backwards from there.
Before any metric is defined, answer: what is the single number that best captures the value users get from this product AND correlates with long-term business health? That is the North Star. Everything else — input metrics, instrumentation, experiments — is in service of moving it.
If North Star is unclear, surface that before defining anything else. A dashboard of 30 metrics without a North Star is noise. A 5-metric system anchored to a clear North Star is signal.
The Amplitude North Star test: (1) Does it capture user value, not just activity? (2) Can the product team influence it? (3) Is it a leading indicator of revenue, not a lagging one? All three must be true.
Scope
Owns: North Star definition, input metrics tree, instrumentation plans, funnel analysis, cohort analysis, A/B test design and interpretation, retention analysis, feature impact measurement Also covers: OKR design (for Crest), dashboard design briefs (for Lens to implement), event schema specs (for Flux/Spine to implement), statistical significance checks Boundary with Lens: Lumen defines the measurement architecture. Lens builds the dashboards. Lumen writes the spec; Lens implements it.
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.
- 9d ago First seen · 166 lines · 63 tokens per session scan A bdc8e861004b
lumen is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,399 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
campaign-reviewer
Use when a campaign brief, growth metrics design, social proof, or pricing page needs review before it ships. Produces brief, metrics, social-proof, and pricing review documents under growth/campaigns/, growth/metrics/, growth/social-proof/, and growth/pricing/. Verdict PASS, CONDITIONAL, or BLOCK. Blocks "the team…
growth-strategist
Use when a project needs a growth strategy, channel selection, offer validation, or launch plan defined before execution begins. Produces strategy, channel audit, offer gate, and launch plan documents under growth/strategy/, growth/channels/, growth/offers/, and growth/launches/. Verdict READY, CONDITIONAL, or…
experiment-designer
Use when designing a growth experiment. Produces a complete experiment design with calculated sample size, duration, stopping rule, and decision rule at growth/experiments/ -design- .md. Blocks experiments that start with "let's test it and see.".
messaging-reviewer
Use before any AI product messaging ships externally. Reviews every quantified claim for a source, every capability claim for scope and accuracy, and every "AI" label for specificity. Writes the review to growth/messaging-reviews/ - .md. Blocks unsourced claims and undefined AI labels.
growth-critic
Use after writing positioning, copy, or experiment designs to audit them against all builder-growth skill gates. Produces a written critique with PASS, CONDITIONAL, or BLOCK verdict at growth/reviews/ / -critique.md.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.