vegastack-cli: Instructions file for Codex

AGENTS.md

vegastack-cli AGENTS.md is an instructions file for Codex, OpenCode from vegastack/vegastack-cli. It costs 1,746 tokens per session, scanned A, original, MIT.

Repository instructions for a command-line tool that gives coding agents searchable Terraform documentation. Terraform is a tool for describing and managing cloud infrastructure in code, and a provider connects it to a specific service.

In plain words
What is it for?
Use it to search documentation for Terraform providers, recent changes, and cross-provider setup examples. Run `vegastack tf` with a query to receive ranked files, knowledge notes, recipes, and related terms.
Why use it?
It explains what the tool contains, how its search output is structured, and which command agents should use. This reduces guesswork when finding Terraform resources, arguments, or import identifiers.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions Claude Code; mentions AGENTS.md.

This is vegastack/vegastack-cli's own configuration. It tells Codex and OpenCode how to work on vegastack-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vegastack-cli configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ( cd ../engg-vegastack-agent-tf-providers && bash scripts/build_bundle.sh --version 0.1.0 ).

Reuse

Borrowing it

Nothing to install: this file belongs to vegastack/vegastack-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vegastack/vegastack-cli/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/vegastack/vegastack-cli

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for vegastack-cli AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vegastack/vegastack-cli/agents-md/github.svg)](https://agentmods.dev/instructions/vegastack/vegastack-cli/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/vegastack/vegastack-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/vegastack/vegastack-cli/agents-md/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.

agentmods 80×15 button for vegastack-cli AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/vegastack/vegastack-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/vegastack/vegastack-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,746 This file is loaded in full into every session.
When invoked 1,746 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01746 $0.01746
Opus 5.5 $0.00698 $0.00698
Sonnet 5.5 $0.00349 $0.00349
Haiku 4.5 $0.00175 $0.00175

Measured 1mo ago against content hash 25f36ce0b3fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vegastack-cli AGENTS.md 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.

AGENTS.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — vegastack-cli

This file is read by Codex, Cursor, Gemini, and any agent that follows the AGENTS.md convention. It tells the agent what this repo is, how to use it, and the rules.

What this repo ships

@vegastack/cli — an npm-installable knowledge harness for coding agents. After npm i -g @vegastack/cli and vegastack skills install, the agent gains:

  • A bundled docs library for 31 Terraform providers (~9,000 markdown files, ~97 MB on disk after extract).
  • A deterministic discovery CLI: vegastack tf "<query>" returns a JSON envelope with ranked files, knowledge cards (recent-change facts), recipes (multi-provider scaffolds), and concept aliases.
  • An Anthropic Agent Skills Standard skill body at skills/vegastack/SKILL.md — read this for the full agent-side mental model.

Skill router

This project ships ONE skill (vegastack) for v0.1.x. v0.2 may split it into:

  • tf-discover — resource/argument/import-id lookup (the heavy CLI invocation path)
  • tf-recipes — cross-provider topology recipes
  • tf-knowledge — recent renames / deprecations / native-feature replacements

For v0.1.x, agents call vegastack tf "<query>" directly. The router pattern is documented here so v0.2's split is non-breaking: the dispatcher will live at this same router section and will only add new skill names, never rename or remove vegastack.

When to use it

Trigger on any of these:

  • "create a <resource>", "terraform for <service>", "how do I deploy X on Y"
  • "what arguments does <resource> accept", "is <resource> deprecated", "import <resource>"
  • Multi-provider topology: zero-trust, scalable backend, GKE+Cloudflare, GitHub Actions → EKS
  • Anything about recent provider changes (renames, deprecations, pricing shifts)

When in doubt, trigger. An invented resource name will fail terraform plan.

How to query

vegastack tf "<the user's natural-language Terraform request>"

The response is a single JSON envelope on stdout. Read these arrays in order:

Read the full file on GitHub · 115 lines

Changes

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.

  1. 1mo ago First seen · 115 lines · 1,746 tokens per session scan A 25f36ce0b3fb

Subscribe to this mod's changes

vegastack-cli AGENTS.md is an instructions file published in the GitHub repository vegastack/vegastack-cli (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,746 tokens to every session, about $0.0070 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.

Related

Other instructions, from other repositories

plan-forge naming.instructions.md

Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.

srnichols/plan-forge · 1,453 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens