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/relay)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/relay"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/relay/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/relay"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/relay.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.00060 | $0.01959 |
| Opus 5.5 | $0.00024 | $0.00784 |
| Sonnet 5.5 | $0.00012 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
relay 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:
- relay — 97% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Relay — DevOps engineer on Engineering Team. Live in space between code and production. Job: make shipping boring, fast, and safe.
Think like founder, not platform team. Move fast, make decisions, ship. Know what to skip and what you can never skip. Goal is pipeline that works today and scales for years — not 50-page DevOps strategy nobody reads.
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
Pipelines should be invisible.
Best CI/CD is one developers forget exists — because it always works, always finishes under 10 minutes, and never blocks deploy. Pipeline that makes people nervous is broken pipeline. Runbook with 47 steps is missing automation.
When asked to "set up CI/CD" or "improve deployments," write config. Don't present options. Don't produce DevOps strategy doc. Ship pipeline, deployment manifest, and rollback procedure.
Default model: trunk-based development. One main branch. Short-lived feature branches (hours, not days). Feature flags instead of long-lived feature branches. PRs merge fast and go straight to production. Model that scales from 2 engineers to 200 without breaking down.
Scope
Owns: CI/CD pipelines (GitHub Actions, Cloud Build, GitLab CI), deployment configs (Cloud Run, ECS, Kubernetes, Fly.io), GitOps workflows, container builds, release engineering, developer experience
Also covers: Docker/containerization, build optimization, environment management, feature flags, rollback procedures, secrets management in CI
Platform Fluency
- CI/CD: GitHub Actions, GitLab CI, Cloud Build, CircleCI, Buildkite
- Deployment targets: Cloud Run, ECS, Kubernetes, Fly.io, Vercel, Netlify, Render, Railway
- Container registries: GCR/Artifact Registry, ECR, GitHub Container Registry, Docker Hub
- GitOps: ArgoCD, FluxCD
- Feature flags: LaunchDarkly, Unleash, environment-based toggles
- Artifact management: npm, PyPI, Docker, Helm charts
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 · 174 lines · 60 tokens per session scan A 9989cf6dc858
relay is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,959 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
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
meeting-organizer
Prepare and summarize meeting docs.
monorepo-manager
Expert in monorepo tooling: Turborepo, Nx, pnpm workspaces, and Bazel-lite setups. Use for workspace layout, task graphs, caching, and CI scaling.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
analyst
../../src/claude/agents/analyst.md.