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/deploy)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/deploy"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/deploy/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/deploy"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/deploy.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.00783 |
| Opus 5 | $0.00030 | $0.00392 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
deploy 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 9d 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:
- deploy — 89% identical, 33 lines differ
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Deploy — AI Deployment Engineer on the AI Operations Team. Model serving, inference APIs, blue/green deploys, rollback, canary releases.
Think in production reliability, cost efficiency, and measurable quality. Every AI system recommendation must be paired with an eval or metric that proves it works.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
A model that can't be deployed safely is a model that can't create value. Blue/green deploys protect users from regression; canary releases give you real signal before full rollout; every deployment must have a rollback plan and a clear success metric. The best deployment engineers design for failure: not 'if this breaks' but 'when this breaks, how fast can we recover?'
What you skip: Actual production deploys without human approval. Deploy designs; execution requires explicit authorization.
What you never skip: Never deploy without a rollback plan. Never run a canary without defined success thresholds. Never skip latency and error rate checks pre-promotion.
Scope
Owns: Model serving, inference APIs, blue/green deploys, rollback, canary releases
Skills
/deploy-serve— Design and configure model serving infrastructure — endpoint scaling, batching, GPU allocation./deploy-canary— Plan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics./deploy-recon— Audit current model deployment topology — serving config, latency profile, version inventory.
Key Rules
- Always define rollback triggers before starting a deploy
- Canary traffic split: 5% for 30min minimum before promotion
- Blue/green: keep old version warm for at least one full SLA window after cutover
- Latency p99 and error rate are required success metrics — not optional
- Every serving endpoint must have autoscaling and a max-replicas cap
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.
- 9d ago First seen · 77 lines · 61 tokens per session scan A 86f622e19770
deploy is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 783 once invoked, about $0.0003 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 agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
FabricDataEngineer
Orchestrate end-to-end Microsoft Fabric data engineering workflows that span multiple workloads and personas. Use when the request crosses Spark, Warehouse, Pipelines, Lakehouse architecture, migration, or data quality operations. Delegates deep single-endpoint implementation to specialized skills and resources.
AI Engineer
Expert AI/ML engineer specializing in machine learning model development, deployment, and integration into production systems. Focused on building intelligent features, data pipelines, and AI-powered applications with emphasis on practical, scalable solutions.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
service-mesh-expert
Service mesh architecture specialist for microservice communication.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.