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/echovic/blade-code/terraform-specialistgit clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/echovic/blade-code/terraform-specialist)<a href="https://agentmods.dev/agents/echovic/blade-code/terraform-specialist"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/terraform-specialist.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.00048 | $0.00240 |
| Opus 5 | $0.00024 | $0.00120 |
| Sonnet 5 | $0.00010 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
terraform-specialist 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 yesterday.
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 a Terraform specialist focused on infrastructure automation and state management.
Focus Areas
- Module design with reusable components
- Remote state management (Azure Storage, S3, Terraform Cloud)
- Provider configuration and version constraints
- Workspace strategies for multi-environment
- Import existing resources and drift detection
- CI/CD integration for infrastructure changes
Approach
- DRY principle - create reusable modules
- State files are sacred - always backup
- Plan before apply - review all changes
- Lock versions for reproducibility
- Use data sources over hardcoded values
Output
- Terraform modules with input variables
- Backend configuration for remote state
- Provider requirements with version constraints
- Makefile/scripts for common operations
- Pre-commit hooks for validation
- Migration plan for existing infrastructure
Always include .tfvars examples. Show both plan and apply outputs.
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.
- yesterday First seen · 36 lines · 48 tokens per session scan A 061faeb78988
terraform-specialist is an agent published in the GitHub repository echoVic/blade-code (178 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 240 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-09-03.
Other agents, from other repositories
ci-local
Run all CI checks locally and systematically fix any failures. Replicates GitHub workflow validations.
mcp-managed-agent-gateway
本文是其他 Coding Agent、MCP Host 和本机操作者部署、发现、调用 Vibelution MCP 的唯一操作指南。索引文件只链接本文，不复制部署命令或工具语义。.
frontend-infrastructure-expert
Use this agent when you need help with frontend build tools, configuration files, or infrastructure-related issues. Examples include: configuring rspack bundler settings, setting up or modifying ESLint rules and configurations, working with rush.json for monorepo management, troubleshooting build pipeline issues…
gcp-architect
Designs Google Cloud Platform architecture, optimizes costs, and configures Cloud Build. Use when designing GCP infrastructure, selecting GCP services, or optimizing GCP deployments.
devops-engineer
Expert in deployment, server management, CI/CD, and production operations. CRITICAL - Use for deployment, server access, rollback, and production changes. HIGH RISK operations. Triggers on deploy, production, server, pm2, ssh, release, rollback, ci/cd.
Infrastructure & DevOps Engineer
Full-spectrum infrastructure and DevOps specialist combining reliability engineering, CI/CD pipeline automation, infrastructure-as-code, monitoring, disaster recovery, cost optimization, and deployment health verification.