Borrowing it
Nothing to install: this file belongs to robinmordasiewicz/terraform-provider-f5xc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robinmordasiewicz/terraform-provider-f5xc/main/.claude/skills/terraform-provider-testing/SKILL.mdgit clone --depth 1 https://github.com/robinmordasiewicz/terraform-provider-f5xcWrote 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/robinmordasiewicz/terraform-provider-f5xc/terraform-provider-testing)<a href="https://agentmods.dev/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-provider-testing"><img src="https://agentmods.dev/badge/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-provider-testing/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/robinmordasiewicz/terraform-provider-f5xc/terraform-provider-testing"><img src="https://agentmods.dev/badge/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-provider-testing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00071 | $0.06138 |
| Opus 5 | $0.00036 | $0.03069 |
| Sonnet 5 | $0.00014 | $0.01228 |
| Haiku 4.5 | $0.00007 | $0.00614 |
Grade A, and why
terraform-provider-testing 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 12d 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 — 831 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Provider Testing Skill
Comprehensive test-driven development for Terraform providers emphasizing iterative co-development of tests, generators, and schemas. This skill drives the development of production-ready provider code through systematic testing and root cause analysis.
Core Philosophy: Never Skip, Always Fix
The Co-Development Mindset
Tests, generators, and schemas are interdependent systems that evolve together. When tests fail, the response is ALWAYS to fix the root cause - never to skip, disable, or work around.
┌─────────────────────────────────────────────────────────────────────────────┐
│ CO-DEVELOPMENT TRIANGLE │
│ │
│ ┌─────────┐ │
│ │ TESTS │ │
│ └────┬────┘ │
│ │ │
│ ┌─────────────────┼─────────────────┐ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │GENERATORS│◄────►│ SCHEMAS │◄────►│ RESOURCES│ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │
│ Tests drive → Generator fixes → Schema corrections → Resource updates │
└─────────────────────────────────────────────────────────────────────────────┘
Never Skip Rules (CRITICAL)
ALWAYS develop and fix unless ONE of these conditions applies:
| Skip Condition | Example | Action |
|---|---|---|
| External cloud credentials required | AWS VPC Site needs AWS_ACCESS_KEY_ID |
t.Skip("requires AWS credentials") |
| Premium/enterprise licensing required | Bot defense needs advanced license | t.Skip("requires premium licensing") |
| Third-party service account needed | External OIDC provider | t.Skip("requires external service account") |
What ships with it
6 files 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.
- 12d ago First seen · 831 lines · 71 tokens per session scan A 64a40f35b319
terraform-provider-testing is a skill published in the GitHub repository robinmordasiewicz/terraform-provider-f5xc (2 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 6,138 once invoked, about $0.0004 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.