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.
npx skills add dryvist/claude-code-plugins --skill terrakube-opsgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/skills/dryvist/claude-code-plugins/terrakube-ops)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/terrakube-ops"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/terrakube-ops/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/skills/dryvist/claude-code-plugins/terrakube-ops"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/terrakube-ops.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.01235 |
| Opus 5.5 | $0.00027 | $0.00494 |
| Sonnet 5.5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
terrakube-ops 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 27d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terrakube operations
Terrakube is a self-hosted remote-execution platform for OpenTofu/Terraform — plans and applies run on its own executor, not on the operator's machine or in CI. This skill is the generic operating model; your own workspace names, hostnames, and credential source stay in your own inventory.
Canonical workflow
tofu login <terrakube-hostname> # once per machine — opens a browser SSO flow
tofu plan # runs remotely; CLI streams the live plan log
tofu apply # same remote workspace, same run
tofu state list # inspect state / outputs afterward
tofu output
tofu plan/apply from the CLI and starting a run from the Terrakube web UI
both drive the same remote executor and the same job log — pick whichever is
convenient; they're interchangeable.
Local
tofu init -backend=false+tofu validatecatches syntax errors without contacting any provider — run that first, it's free and instant compared to a remote plan.
Never use a targeted apply
A targeted apply (-target=...) can leave the real infrastructure and any
downstream-published inventory describing two different worlds — whatever
consumes that inventory (configuration management, DNS, monitoring) now
disagrees with reality. Apply the reviewed whole-workspace plan. For
state surgery, prefer moved/removed blocks over -target or manual state
edits.
Workspace locking and recovery
Terrakube owns one run queue and one lock per workspace — a second run simply queues behind the active one; independent workspaces don't share a lock.
- Cancel a genuinely stuck run from the workspace UI, not by force-unlocking blind.
- Confirm the executor has actually stopped before force-cancelling or unlocking — cancelling a run that's still writing state is how corruption happens.
- Prefer fixing forward (revert the config change in git, plan/apply again) over restoring an older state version. When state genuinely is corrupted, preserve the current state version before restoring an older one — you may need to diff them later.
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.
- 27d ago Changed · -28 tokens per session 2fb6ab30b205
- 1mo ago First seen · 118 lines · 96 tokens per session scan A f4040833decb
terrakube-ops is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 1,235 once invoked, about $0.0003 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-04.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
agent-cloud-architect
Specialist subagent: 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…
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
cloudflare-ops
Cloudflare Workers + Wrangler edge ops: runtime, bindings, local dev, secrets, deploy/CI, Pages-vs-Workers. Triggers on: cloudflare workers, wrangler, wrangler deploy, wrangler.toml, KV, D1, R2, durable objects, queues, vectorize, compatibilitydate, edge functions, illegal invocation, waitUntil, caches API, smart…
hono-ops
Hono on Cloudflare Workers - composition, middleware, typed bindings, validation, RPC, streaming, testing. Use for: hono, hono middleware, app.route, hono rpc, c.env bindings, onError, zValidator, vitest-pool-workers, spa fallback worker.