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.5 | $0.00021 | $0.00316 |
| Sonnet 5.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 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.
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.
- 1mo 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,876 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 789 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
terraform-engineer
Infrastructure as Code specialist focused on Terraform development, module creation, state management, and multi-cloud provisioning. Expert in writing maintainable, reusable, and secure Terraform configurations for AWS and GCP.
arn-infra-change-reviewer
This agent should be used when the arn-infra-review-change skill or arn-infra-execute-change skill needs a structured quality review of completed infrastructure changes. It evaluates security posture, cost compliance, blast radius adherence, rollback documentation, environment parity, state consistency, and resource…
arn-infra-cost-analyst
This agent should be used when infrastructure changes need cost estimation before deployment, when the user wants to understand the cost impact of their current or planned infrastructure, or when spend thresholds need enforcement. It integrates with Infracost when available and provides usage-based pricing estimates…
arn-infra-reference-researcher
This agent should be used when the arn-infra-refresh skill needs to research online for the latest versions of infrastructure tools, MCP servers, CLI tools, base images, and patterns. It compares against current reference file content and produces a structured update report. Context: Invoked by arn-infra-refresh…
arn-infra-verifier
This agent should be used when a deployment needs post-deployment verification to confirm that infrastructure is healthy, endpoints are reachable, DNS resolves correctly, SSL certificates are valid, and resource state matches the expected topology. It recommends rollback when verification checks fail. Context: Invoked…
arn-infra-request-analyzer
This agent should be used when an infrastructure request issue needs analysis to determine what cloud resources, configuration changes, and infrastructure work are required. It navigates to the application project, reads Arness Core artifacts (feature specs, plans, codebase patterns, source code), and produces a…