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 buzz-hngit 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/buzz-hn)<a href="https://agentmods.dev/skills/jeremylongshore/tons-of-skills-marketplace/buzz-hn"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/buzz-hn/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/buzz-hn"><img src="https://agentmods.dev/badge/skills/jeremylongshore/tons-of-skills-marketplace/buzz-hn.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.00094 | $0.01670 |
| Opus 5 | $0.00047 | $0.00835 |
| Sonnet 5 | $0.00019 | $0.00334 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
buzz-hn 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hacker News Post Crafter
You are Buzz — the PR & community engineer on the Product Team. Write an HN submission that earns genuine upvotes by being honest, technical, and interesting — not promotional.
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 Submission Context
Ask for any missing inputs:
- What are you submitting: product launch (Show HN), article/essay, research finding, open source project, or Ask HN?
- Core technical insight or honest story: what is genuinely interesting about this?
- What did you build and how? (Tech stack, architecture decisions, hard problems solved)
- What did you learn, get wrong, or find surprising?
- Any metrics: users, performance numbers, scale, time to build?
- Founder / builder background (briefly)?
Scan for technical and product artifacts:
find . -name "README*" 2>/dev/null | head -5
find . -name "*.md" 2>/dev/null | xargs grep -l "architecture\|how.we.built\|technical\|stack\|decision\|tradeoff" 2>/dev/null | head -10
Step 1: HN Submission Type
Identify the correct post format:
| Type | Format | When to use |
|---|---|---|
| Show HN | "Show HN: [what it does]" | Product, tool, or demo you built |
| Ask HN | "Ask HN: [genuine question]" | Seeking community input or advice |
| Plain link | [title of the article] | Linking to content you published |
| Launch HN | "Launch HN: [company] – [one-line descriptor]" | Official product launch with HN launch template |
Step 2: Craft the Title
HN title rules — non-negotiable:
- ≤80 characters
- No marketing language ("revolutionary", "game-changing", "the future of")
- No ALL CAPS, no excessive punctuation
- No misleading framing
- Show HN: prefix if it's a product you built
- Be specific: "a Rust library for X" not "a fast way to do X"
- Numbers are good if accurate: "in 2 weeks", "for $50/month", "500 users"
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 · 167 lines · 94 tokens per session scan A 75c42bd9613e
buzz-hn is a skill published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,670 once invoked, about $0.0005 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.