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 ihatesea69/kiro-kit --skill terraform-modulesgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/terraform-modules)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/terraform-modules"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/terraform-modules/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/ihatesea69/kiro-kit/terraform-modules"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/terraform-modules.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.00028 | $0.00300 |
| Opus 5 | $0.00014 | $0.00150 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
terraform-modules 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 7d 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
Terraform Modules
Activate this skill when designing or implementing Terraform modules.
When to Use
- Creating reusable infrastructure components
- Refactoring inline resources into modules
- Designing module interfaces (variables, outputs)
- Testing infrastructure code
- Publishing modules to registries
Module Structure
modules/<module-name>/
main.tf Primary resource definitions
variables.tf Input variables with descriptions and validation
outputs.tf Output values for consumers
versions.tf Provider and Terraform version constraints
README.md Usage documentation with examples
examples/ Example configurations
tests/ Terratest or terraform test files
Design Principles
- Single responsibility: one module, one concern
- Sensible defaults: work out of the box with minimal config
- Explicit interfaces: all inputs documented with types and validation
- Composable: modules should compose with other modules cleanly
- Testable: include examples that can be used as integration tests
Rules
- Pin provider versions in versions.tf
- Add validation blocks to variables where appropriate
- Use
terraform fmtbefore committing - Include at least one working example
- Document all variables and outputs
- Use data sources over hardcoded values
- Never hardcode account IDs, regions, or environment names
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.
- 7d ago First seen · 48 lines · 28 tokens per session scan A bcfc7286a81a
terraform-modules is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 300 once invoked, about $0.0001 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 skills, from other repositories
awesome-azd-template-submit
Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
expo-dev-client
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
expo-eas-update
Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
lizard-core
Core Lizard CLI usage guide. Read this before running any lizard commands. Covers the full app lifecycle (login, init, link, add, up, redeploy, logs, events, status, scale, restart, secrets, domains, run, ssh, metrics), the workspace → project → service model, managed addons (postgres, redis, s3 with auto-public…
setup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.