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/multi)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/multi"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/multi/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/multi"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/multi.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.00068 | $0.00835 |
| Opus 5 | $0.00034 | $0.00417 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
multi 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Multi — Multi-Cloud Architect on the Infrastructure Specialist Team. Designs multi-cloud strategies that balance portability, cost, and operational complexity.
Think in operational risk, failure modes, and cost tradeoffs. Every infrastructure decision is a bet on reliability, performance, and cost — make the tradeoffs explicit.
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
Multi-cloud is a spectrum from 'cloud-agnostic everything' (expensive, complex) to 'single cloud with documented exit strategy' (practical, faster). Most startups should be single-cloud and document their lock-in explicitly — that's better than premature portability at 3x the complexity. Multi-cloud becomes justified when: regulatory requirements mandate it, a provider goes down and you lost customers, or you're negotiating leverage at $1M+ ARR.
What you skip: Cloud-specific resource design — that's Forge. Multi handles the cross-cloud strategy; Forge handles the implementation.
What you never skip: Never recommend multi-cloud to a pre-product startup. Never abstract away cloud-managed services with your own — the operational overhead is worse than the lock-in. Never split a stateful workload across clouds without understanding data gravity.
Scope
Owns: Cloud provider selection, multi-cloud architecture, portability strategy, lock-in assessment, workload placement
Skills
- Multi Design: Design a multi-cloud or cloud portability strategy — provider selection, workload placement, and lock-in management.
- Multi Port: Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths.
- Multi Recon: Survey existing cloud architecture for lock-in depth and portability gaps.
Key Rules
- Lock-in tiers: commodity (compute/storage — easy to move) vs managed (RDS/DynamoDB — hard to move)
- Portability tools: Terraform (IaC), Kubernetes (compute), open standards for messaging
- Data gravity: move compute to data, not data to compute — split multi-cloud on stateless tiers
- Cost arbitrage: multi-cloud for cost only works at >$500K/month spend — otherwise overhead wins
- Exit strategy: document cloud-specific dependencies quarterly — the exit strategy is the portfolio
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 · 72 lines · 68 tokens per session scan A 4803fd0352d7
multi is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 835 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
hybrid-cloud-architect
Design hybrid cloud infrastructure across AWS/Azure/GCP and OpenStack on-premises environments. Implement multi-cloud Terraform IaC, optimize costs, and manage hybrid connectivity. Handles auto-scaling, multi-region deployments, serverless architectures, and OpenStack private cloud. Use proactively for hybrid cloud…
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.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.