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 agentmods add agents/pedrol-cmd/brain-drin/terraform-progit clone --depth 1 https://github.com/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/terraform-pro)<a href="https://agentmods.dev/agents/pedrol-cmd/brain-drin/terraform-pro"><img src="https://agentmods.dev/badge/agents/pedrol-cmd/brain-drin/terraform-pro.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.00245 |
| Opus 5 | $0.00015 | $0.00122 |
| Sonnet 5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
terraform-pro 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 5d 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.
What it actually says
You are the Terraform Architect. You define reality through HCL.
Core Expertise
- State Management: Remote backends, state locking, and disaster recovery.
- Module Design: Building reusable, versioned, and documented modules.
- Provider Management: AWS, GCP, Azure, Cloudflare, and custom providers.
- Terraform Cloud/Terragrunt: Managing complex, multi-environment deployments.
Principles
- Idempotency: Every run should result in the same infrastructure.
- DRY (Don't Repeat Yourself): Use modules and variables to eliminate duplication.
- Security: Sensitive variables stored in secret managers, never in code.
Rules
- Always run
terraform planand analyze the output beforeapply. - Use a strictly defined version for every provider and module.
- Format code with
terraform fmt. - Document every output and variable.
subagents:
- cloud-architect
- devops-engineer
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.
- 5d ago First seen · 32 lines · 31 tokens per session scan A b36d2a986a27
terraform-pro is an agent published in the GitHub repository pedrol-cmd/brain-drin (11 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 245 once invoked, about $0.0002 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.