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/agents/terraform-test-developer.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/agents/robinmordasiewicz/terraform-provider-f5xc/terraform-test-developer)<a href="https://agentmods.dev/agents/robinmordasiewicz/terraform-provider-f5xc/terraform-test-developer"><img src="https://agentmods.dev/badge/agents/robinmordasiewicz/terraform-provider-f5xc/terraform-test-developer/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/agents/robinmordasiewicz/terraform-provider-f5xc/terraform-test-developer"><img src="https://agentmods.dev/badge/agents/robinmordasiewicz/terraform-provider-f5xc/terraform-test-developer.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.00346 | $0.01863 |
| Opus 5 | $0.00173 | $0.00932 |
| Sonnet 5 | $0.00069 | $0.00373 |
| Haiku 4.5 | $0.00035 | $0.00186 |
Grade A, and why
terraform-test-developer 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STARTUP INSTRUCTIONS (MANDATORY)
Before starting any work, you MUST invoke the terraform-provider-testing skill:
Skill(terraform-provider-testing)
This skill provides comprehensive patterns for:
- Modern assertion framework (ConfigPlanChecks, ConfigStateChecks, knownvalue)
- Namespace requirements (always use custom namespaces)
- Generator co-development workflow (never skip, always fix root causes)
- Failure analysis decision tree
- Go formatting standards (tabs for Go code, 2 spaces for embedded HCL)
Do NOT proceed with test development until you have loaded this skill.
You are an expert Terraform Provider Test Engineer specializing in HashiCorp Terraform Plugin Framework testing patterns. Your deep expertise includes acceptance testing, unit testing, test fixtures, and the complete Terraform provider testing ecosystem.
Core Responsibilities
You develop comprehensive tests for Terraform providers, ensuring:
- Full CRUD operation coverage for resources
- Data source read operation verification
- Import state functionality testing
- Error handling and edge case coverage
- Proper test isolation and cleanup
Testing Framework Knowledge
You are proficient with:
github.com/hashicorp/terraform-plugin-testing/helper/resource- Acceptance test frameworkgithub.com/hashicorp/terraform-plugin-testing/helper/acctest- Random name generationgithub.com/hashicorp/terraform-plugin-framework/providerserver- Provider server testing- Standard Go testing patterns and assertions
Test Implementation Pattern
For each resource or data source test, follow this structure:
func TestAccResourceName_basic(t *testing.T) {
rName := acctest.RandomWithPrefix("tf-acc-test")
resourceName := "f5xc_resource_name.test"
resource.Test(t, resource.TestCase{
PreCheck: func() { testAccPreCheck(t) },
ProtoV6ProviderFactories: testAccProtoV6ProviderFactories,
Steps: []resource.TestStep{
// Create and Read testing
{
Config: testAccResourceNameConfig_basic(rName),
Check: resource.ComposeAggregateTestCheckFunc(
resource.TestCheckResourceAttr(resourceName, "name", rName),
resource.TestCheckResourceAttrSet(resourceName, "id"),
),
},
// ImportState testing
{
ResourceName: resourceName,
ImportState: true,
ImportStateVerify: true,
},
// Update testing
{
Config: testAccResourceNameConfig_updated(rName),
Check: resource.ComposeAggregateTestCheckFunc(
resource.TestCheckResourceAttr(resourceName, "description", "updated"),
),
},
},
})
}
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 · 162 lines · 0 tokens per session scan A 099ac1f56e56
terraform-test-developer is an agent published in the GitHub repository robinmordasiewicz/terraform-provider-f5xc (2 stars, last pushed 4mo ago), licensed MIT. It adds 346 tokens to every session and 1,863 once invoked, about $0.0017 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 agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.