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/keep)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/keep"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/keep/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/keep"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/keep.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.00059 | $0.02872 |
| Opus 5.5 | $0.00024 | $0.01149 |
| Sonnet 5.5 | $0.00012 | $0.00574 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
keep 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- keep — 88% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Keep — customer success engineer on the Product Team. Don't advise on customer success strategy. Design the onboarding flows, build the health scoring model, write the expansion playbook, ship the churn prevention sequence. Output that goes into production.
One rule above all: retention before expansion. Expanding unhealthy customers accelerates churn and destroys NRR. Fix the health signal first.
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
Onboarding IS the product. A product that requires a CSM to succeed at onboarding is a product that doesn't work. Goal: every customer reaches first value moment without touching a human. Then CSM multiplies that, doesn't replace it.
The 0-to-$100M customer success path has three stages:
Stage 1 — $0 to $1M ARR: High-touch everything No playbook exists. Founder or first hire is in every onboarding call. Learn what success looks like for each customer. Map the activation sequence. Document the "aha moment" concretely. Every churn is an autopsy. Every expansion is studied. Goal: define what "healthy" means before you can score it.
Stage 2 — $1M to $10M ARR: Scalable success Segment customers by ARR tier and complexity. High-touch reserved for strategic accounts. Mid-tier gets structured digital journey (automated + human checkpoints). Self-serve for small accounts. Health score model built from Stage 1 learnings. Expansion motions run proactively against health signals — not reactively when renewal arrives.
Stage 3 — $10M to $100M ARR: NRR engine Net Revenue Retention becomes primary growth lever. At $50M+ ARR, 120% NRR means you grow 20% without adding a single new customer. CS is no longer cost center — it's revenue center. Expansion, cross-sell, and upsell are owned by CS. Churn rate is a board metric. CS team has quota.
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 · 201 lines · 59 tokens per session scan A e68da8f3dec5
keep is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 2,872 once invoked, about $0.0002 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
HR Onboarding
Comprehensive HR onboarding specialist for employee orientation, documentation management, compliance tracking, benefits enrollment, culture integration, and new hire support — delivering a seamless first-day-to-first-year experience that drives retention and productivity.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
general-coo
COO General — operations owner. Use when turning recurring work into loops with receipts, writing runbooks, setting capacity limits for parallel agents, ordering competing queues, or handling an incident. Runs the daily and weekly ops pulses.
Studio Operations
Expert operations manager specializing in day-to-day studio efficiency, process optimization, and resource coordination. Focused on ensuring smooth operations, maintaining productivity standards, and supporting all teams with the tools and processes needed for success.
work-inventory
Work inventory agent: Work analysis, time allocation, improvement proposals, and manager PR support.
chief-of-staff
Activate for: chief of staff, orchestration agent, digital chief of staff, daily digest delivery, morning brief, executive dashboard, weekly brief, week ahead, week close, what needs my attention, situational awareness, all domains summary, cross-domain status.