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 vynazevedo/first-plan --skill lens-terraformgit clone --depth 1 https://github.com/vynazevedo/first-planWrote 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/vynazevedo/first-plan/lens-terraform)<a href="https://agentmods.dev/skills/vynazevedo/first-plan/lens-terraform"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/lens-terraform/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/vynazevedo/first-plan/lens-terraform"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/lens-terraform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00920 |
| Opus 5 | $0.00026 | $0.00460 |
| Sonnet 5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
first-plan-lens-terraform 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 10d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens Terraform / IaC
Detecção
*.tfem qualquer pasta*.tofu(OpenTofu)Pulumi.yaml(Pulumi - alternativa, mas não Terraform)cdk.json(AWS CDK)serverless.yml(Serverless Framework)
Estrutura
Layout comum
infra/
├── modules/ módulos reutilizáveis
│ ├── network/
│ ├── compute/
│ └── database/
├── environments/ ou `live/`
│ ├── dev/
│ ├── staging/
│ └── prod/
└── shared/ providers, vars compartilhadas
Variantes:
- Workspaces (
terraform workspace) - menos comum em produção - Pasta única com tfvars por env
Detectar
- Onde está o root módulo (entry para
terraform apply)? - Há módulos em
modules/? - Há separação por env (
environments/<env>/main.tf)? - Quais providers usados? (aws, azure, gcp, kubernetes, helm, etc)
Backend de state
backend "s3"+ DynamoDB lock?backend "azurerm"oubackend "gcs"?backend "remote"(Terraform Cloud)?- Local state (
backend "local") - red flag para prod
Versionamento
terraform.required_versionpinned?required_providerscom versão pinned?.terraform-version(tfenv) ou.tool-versions(asdf)?
Convenções
Naming
- Recursos:
<projeto>-<ambiente>-<componente>? - Tags obrigatórias: Environment, Project, Owner, CostCenter?
- Module naming convention
Variables
variables.tf+outputs.tfem cada móduloterraform.tfvarsou*.auto.tfvars?- Validation blocks?
- Sensitive marking?
Outputs
- Outputs nomeados consistentemente
- Modulos consumidos via
module.X.output_name? - Outputs sensíveis marcados?
Padrões de segurança
- Hardcoded secrets? (red flag)
- Use de
aws_secretsmanager,vault,sops - IAM least privilege?
- Encryption at rest configurada nos resources
CI/CD
terraform planem PR?- Atlantis, terraform-cloud, scalr, env0?
- GitHub Actions / GitLab CI / etc.
Testing
terratest(Go-based)?kitchen-terraform?tflint,tfsec,checkovem CI?
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.
- 10d ago First seen · 128 lines · 52 tokens per session scan A 964e1bb01712
first-plan-lens-terraform is a skill published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 16d ago), licensed MIT. It adds 52 tokens to every session and 920 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-08-30.
Other skills, from other repositories
cross-repo-testing
This skill should be used when the user asks to "test a cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud", "e2e test a cloud workspace feature", "test provider tokens", "test secrets inheritance", or when changes span the SDK and OpenHands server repos and need end-to-end…
open-forge
Automate self-hosting of open-source apps on cloud infrastructure the user owns. Use when the user asks to "self-host", "deploy to my own cloud", "install X on AWS / Lightsail / EC2 / Azure / Hetzner / DigitalOcean / GCP / Oracle Cloud / Hostinger / Raspberry Pi / Kubernetes / Fly.io / Render / Railway / Northflank /…
RecallMax
Enhances AI memory capabilities with long-context support.
roo-bedrock-custom-arn
Roo Code's Bedrock provider silently disables caching for custom ARNs. Populate cachableFields to fix.
agent-memory
Persistent memory system for AI coding agents. Use when you need to save facts about the user, store interaction preferences, log session events, or search previously saved memories. Triggers on remembering, saving context, recalling past decisions, or when the user says "remember this". Also use proactively when the…
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.