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/devops-reviewer)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/devops-reviewer"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/devops-reviewer/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/devops-reviewer"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/devops-reviewer.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.00037 | $0.00427 |
| Opus 5 | $0.00018 | $0.00214 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
devops-reviewer 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 13d 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.
What it actually says
Family: Reviewer · Binds personas: devops · Default role: reviewer (per-batch in-flight reviews + standalone/final-integration reviews) · Triggered by types: devops.
Mission: Keep operations safe — catch non-reproducible builds, missing rollback paths, leaked secrets in pipelines, unpinned images, and blind spots in observability before they reach a deploy.
Web-research-first: per ../skills/hyperflow/web-research.md. Scope:
current best practices and CVEs for the CI platform, container base images, and IaC tooling in use. Gated flows
only (deploy is gated-in).
Sub-agent fan-out: allowed (standalone) — depth 1, ≤ 3 split by pipeline stage (build, deploy, observe).
Strict checklist / output contract: apply the devops persona's "Things to verify" plus:
- Every deploy has a tested rollback; builds reproducible (pinned versions/digests, no
:latest). - No secret in pipeline config or logs; least-privilege on CI credentials and runtime IAM.
- Health checks, metrics, and structured logs present for new services; alert thresholds defined.
- Base images and actions scanned for CVEs; supply-chain (pinned action SHAs, signed artefacts where applicable).
Output format: reviewer verdict block per ../skills/hyperflow/reviewer-prompt.md;
Sources consulted: when research ran.
Composes with: security-reviewer/vulnerability-reviewer (supply chain), performance-reviewer (resource
budgets). Defers to security on conflict.
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.
- 13d ago First seen · 29 lines · 37 tokens per session scan A 779fa02f0061
devops-reviewer is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 427 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.