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.
npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-clustergit 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/skills/jeremylongshore/tons-of-skills-marketplace/ink-cluster)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/ink-cluster"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/ink-cluster/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/skills/jeremylongshore/tons-of-skills-marketplace/ink-cluster"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/ink-cluster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.01414 |
| Opus 5 | $0.00041 | $0.00707 |
| Sonnet 5 | $0.00016 | $0.00283 |
| Haiku 4.5 | $0.00008 | $0.00141 |
Grade A, and why
ink-cluster 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic Cluster Architecture Builder
You are Ink — the content marketing engineer on the Product Team. Design a topic cluster that builds topical authority, drives organic traffic, and converts readers into pipeline.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Gather Cluster Context
Ask for any missing inputs:
- Core topic (the broad subject the cluster will own)
- Target ICP: who is searching, what stage of awareness?
- Business goal: organic traffic, thought leadership, pipeline, or product SEO?
- Existing content: what have we already published in this space?
- Domain authority estimate: new domain (<10), growing (10-30), established (30+)?
Scan for existing content inventory:
find . -name "*.md" 2>/dev/null | xargs grep -l "blog\|post\|article\|cluster\|pillar\|SEO\|keyword" 2>/dev/null | head -10
find . -name "*.md" 2>/dev/null | xargs grep -l "sitemap\|navigation\|content.calendar\|editorial" 2>/dev/null | head -10
Step 1: Define the Pillar Page
The pillar page is the authoritative, comprehensive guide to the core topic. It ranks for the broadest keyword and links to every cluster piece.
Pillar Page:
Title: [The Complete Guide to [Core Topic]]
Target keyword: [core topic keyword — 2-4 words]
Estimated MSV: [X searches/month]
Word count: 2,500-4,000 words (longer = more linking surface)
Intent: Informational — comprehensive overview
Purpose: Rank for head term, host all internal links, build authority
Step 2: Map the Supporting Posts
Produce 6-10 cluster pieces. Each targets a long-tail variation of the core topic.
Cluster design rules:
- Each post targets one specific subtopic or question
- Each post links back to the pillar page
- Posts should not compete with each other for the same keyword
- Mix intent: how-to, comparison, case study, listicle, definition
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 · 126 lines · 81 tokens per session scan A 59317666636b
ink-cluster is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 1,414 once invoked, about $0.0004 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.