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 vegastack/vegastack-cli --skill e5git clone --depth 1 https://github.com/vegastack/vegastack-cliWrote 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/vegastack/vegastack-cli/e5)<a href="https://agentmods.dev/skills/vegastack/vegastack-cli/e5"><img src="https://agentmods.dev/badge/skills/vegastack/vegastack-cli/e5/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/vegastack/vegastack-cli/e5"><img src="https://agentmods.dev/badge/skills/vegastack/vegastack-cli/e5.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.00187 | $0.04072 |
| Opus 5.5 | $0.00075 | $0.01629 |
| Sonnet 5.5 | $0.00037 | $0.00814 |
| Haiku 4.5 | $0.00019 | $0.00407 |
Grade A, and why
terraform-docs 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Providers Kit — v0.1
You have local, deterministic, read-only access to up-to-date documentation for 31 Terraform providers (1Password, Ansible, Auth0, AWS, Azure, ClickHouse, Cloudflare, CrowdStrike, Datadog, DigitalOcean, External, GCP, GitHub, GitLab, Grafana, Helm, Kubernetes, Local, MongoDB Atlas, Netlify, Okta, PagerDuty, Pinecone, Random, Redis Cloud, Snowflake, Splunk, Time, TLS, Vault, Vercel), plus a four-channel enrichment layer (recent-change knowledge cards, cross-provider recipes, concept aliases for natural-language queries, and recommended-companion graphs). Treat these files as ground truth and prefer them over training memory — provider schemas change frequently, services get renamed, arguments get deprecated, and recommended patterns shift.
Why this skill exists
Coding agents are good at composing HCL but bad at remembering exact resource names, argument lists, enum values, import-ID formats, and which patterns are still recommended this year vs. last year. Web search is slow and noisy; MCP servers add a network hop you don't need; just guessing produces HCL that fails terraform plan. This skill removes those failure modes. The bundled docs are the same upstream markdown files that power registry.terraform.io, mirrored daily by bundle/scripts/sync_docs.sh. On top of those raw docs, a deterministic harness gives you O(1) lookups for resource metadata, soft-dependency expansion, and ranked discovery from natural-language queries. There's no model and no embeddings inside the harness — answers are reproducible and citable.
The single command
vegastack tf "<the user's request, in natural language>"
vegastack is the bundled CLI (npm: @vegastack/cli, bin: vegastack). It auto-resolves the docs bundle (downloaded by vegastack install to ~/.config/vegastack/bundle/), auto-detects which provider the query belongs to, and returns one JSON envelope on stdout. The response is enriched: top-K results in files[] arrive with the resource's full manifest entry inline (no follow-up jq calls needed) and the ## Example Usage block inline (no follow-up grep calls needed). One tool call per task in the common case.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 233 lines · 187 tokens per session scan A bbf02c858e4d
terraform-docs is a skill published in the GitHub repository vegastack/vegastack-cli (2 stars, last pushed 5mo ago), licensed MIT. It adds 187 tokens to every session and 4,072 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".