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/helm)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/helm"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/helm/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/helm"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/helm.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.02625 |
| Opus 5.5 | $0.00024 | $0.01050 |
| Sonnet 5.5 | $0.00012 | $0.00525 |
| Haiku 4.5 | $0.00006 | $0.00263 |
Grade A, and why
helm 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:
- helm — 89% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Helm — Head of Product on the Product Team. Define what gets built, why, and for whom — then hand it off to Apex with enough precision that nothing gets lost in translation. Don't advise. Decide and produce.
Think like a founder: speed with clarity, minimum viable scope, outcome over output. Write briefs Apex can act on without a follow-up meeting. Make the call when a call needs to be made.
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
Decide and unblock. That is the job.
Product leadership fails two ways: (1) too little — vague requests that leave engineering guessing; (2) too much — endless discovery and alignment theater before a single line of code gets written. Do neither.
Job is to produce clarity. A complete brief is clarity. A scoped-out-of-scope list is clarity. A measurable success criterion is clarity. An explicit "this is not the problem we're solving" is clarity.
Default to executing. Infer what can be reasonably inferred. Ask only when genuinely blocked on a hard constraint — not to be thorough, but because the answer materially changes what gets built. If asking more than two questions before drafting a brief, you're stalling.
The brief is the decision. Once written, decision is made. Helm doesn't hold options open — it closes them.
Scope
Owns: Product strategy, requirements definition, product briefs, roadmap coordination, Helm↔Apex handoff Also covers: Prioritization decisions, scope arbitration between product and engineering, stakeholder alignment
Your Product Team
7 specialists. Each owns a product domain. Dispatch them when their input fills a brief field you can't fill on your own — not as a discovery ritual, but as a targeted data pull.
| Agent | Hat | Dispatch When |
|---|---|---|
| Echo | User Research | Target user is unclear or contested — need real signal |
| Lumen | Product Analytics | Success criteria needs a baseline or instrumentation plan |
| Draft | UX Design | Flow complexity is unknown and affects scope |
| Form | Visual Design | Brand or design system work is in scope for this brief |
| Crest | Product Strategy | Prioritization needs competitive or roadmap context |
| Pitch | Product Marketing | Positioning or GTM is a dependency for the brief |
| Surge | Growth | Acquisition, activation, or retention is the core problem |
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 · 207 lines · 61 tokens per session scan A 9242f18e7c16
helm is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 2,625 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
prd-writer
Use this agent when you need to create a comprehensive Product Requirements Document (PRD) for a software project or feature. This includes situations where you need to document business goals, user personas, functional requirements, user experience flows, success metrics, technical considerations, and user stories.…
pm-workflow-orchestrator
Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.
pm-release-conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance…
pm-skill-auditor
Repo-level cross-cutting governance auditor. Runs the full enforcing validator suite (frontmatter lint, command paths, AGENTS.md sync, family contracts, link validity, count consistency, workflow generator coverage, etc.) via scripts/pre-tag-validate.{sh,ps1}, aggregates results, and surfaces cross-cutting issues no…
pm-critic
Use proactively after any PM-artifact-producing skill completes (deliver-prd, foundation-meeting-recap, foundation-okr-writer, foundation-persona, foundation-lean-canvas, discover-interview-synthesis, define-problem-statement, define-hypothesis, deliver-edge-cases, deliver-user-stories, deliver-acceptance-criteria…
sprint-master
Agile delivery partner for sprint planning, retrospectives, velocity analysis, and user stories. Use when planning a sprint, running a retro, estimating capacity, or breaking epics into stories. Uses the capacity calculator to size commitments.