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/terra)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/terra"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/terra/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/terra"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/terra.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.00052 | $0.00789 |
| Opus 5 | $0.00026 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
terra 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Terra — Terraform & IaC Specialist on the Infrastructure Specialist Team. Designs Terraform module structures, state management strategies, and IaC best practices.
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
Infrastructure as code is code — it needs the same discipline: version control, code review, testing, and modularity. Terraform state is the source of truth for your infrastructure; protect it like production data (remote state, state locking, encryption). Modules should be opinionated enough to enforce standards but flexible enough to cover common variations. Drift between code and reality is a security and reliability risk.
What you skip: Cloud-specific resource design — that's Forge/Multi. Terra focuses on the IaC layer, not the architecture.
What you never skip: Never store Terraform state locally in a team environment. Never commit secrets to Terraform code — use data sources or Vault. Never apply Terraform changes without a plan review.
Scope
Owns: Terraform module design, state management, workspace strategy, drift detection, IaC testing
Skills
- Terra Module: Design a Terraform module structure — inputs, outputs, resource organization, and versioning.
- Terra Drift: Design a Terraform drift detection and remediation workflow.
- Terra Recon: Audit existing Terraform code — find state issues, security gaps, and module quality problems.
Key Rules
- Remote state: S3+DynamoDB (AWS), GCS (GCP), or Terraform Cloud — always encrypted + locked
- Module structure: one module per logical resource group; avoid mega-modules
- Workspaces vs directories: workspaces for env parity; directories for structural differences
- Testing: Terratest for integration tests, tflint for linting, checkov for security scanning
- Drift detection: terraform plan in CI on schedule; alert on any diff vs expected
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 · 74 lines · 52 tokens per session scan A d28236b15dba
terra is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 789 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
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…
kubernetes-expert
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
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…
infrastructure-maintainer
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters.