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 skills/soulcodex/agentic/create-terraform-testsnpx skills add soulcodex/agentic --skill create-terraform-testsgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/create-terraform-tests)<a href="https://agentmods.dev/skills/soulcodex/agentic/create-terraform-tests"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/create-terraform-tests.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.00044 | $0.00564 |
| Opus 5 | $0.00022 | $0.00282 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
create-terraform-tests 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Terraform Tests Skill
Author Terraform test coverage for AWS modules.
Always pair this skill with terraform-risk-playbook. That skill is
authoritative for the response contract, risk classification, version/runtime
guards, validation chain, and rollback notes.
Authoritative precedence: when this skill and terraform-infrastructure are both
active, this skill is authoritative for module testing strategy, test layout,
and assertion patterns.
Step 1 - Identify Risk-Critical Behaviors
Prioritize tests for:
- security controls (encryption, public exposure prevention)
- destructive change prevention for stateful resources
- required inputs and invalid configuration rejection
- output contract stability
- identity and address migration safety (
count/for_each,movedflows) - provider/runtime upgrade compatibility when version constraints change
Step 2 - Implement Terraform-Native Test Layout
Use tftest-patterns.md for baseline structure and pattern selection.
Minimum coverage:
- happy path apply/plan expectations
- invalid input validation checks
- policy/security checks for sensitive resources
- choose
command = applywhen assertions depend on computed values or set-type nested blocks
Step 3 - Add CI-Friendly Validation Chain
Ensure deterministic checks in CI:
terraform fmt -check -recursiveterraform init -backend=falseterraform validateterraform test
CI safety guardrails:
- do not point tests at production/shared backends
- use ephemeral credentials/accounts for apply-capable tests
- skip or scope tests when required cloud credentials are not present
- if the risk category includes compliance or secret exposure, include the repo's existing policy/security checks where applicable
Step 4 - Keep Tests Bounded
Use minimal fixtures and avoid long-running integration behavior unless explicitly requested. Document emulator vs real-AWS assumptions clearly.
Step 5 - Report Coverage Gaps
Summarize what is covered, known blind spots, and next highest-value tests. Call out whether each scenario is plan-only confidence, emulator confidence, or real-cloud confidence.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 82 lines · 44 tokens per session scan A e17e0eda5300
create-terraform-tests is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 564 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-31.
Other skills, from other repositories
aws-cloud-architecture
Comprehensive guide to AWS cloud architecture covering compute, storage, databases, networking, security, serverless, and cost optimization with production-ready patterns.
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).