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/commands/test-resources.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/commands/robinmordasiewicz/terraform-provider-f5xc/test-resources)<a href="https://agentmods.dev/commands/robinmordasiewicz/terraform-provider-f5xc/test-resources"><img src="https://agentmods.dev/badge/commands/robinmordasiewicz/terraform-provider-f5xc/test-resources/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/commands/robinmordasiewicz/terraform-provider-f5xc/test-resources"><img src="https://agentmods.dev/badge/commands/robinmordasiewicz/terraform-provider-f5xc/test-resources.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.00000 | $0.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
test-resources 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 11d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Resource Test Development
Spawn multiple terraform-test-developer agents in parallel to develop tests for the specified resources.
Usage
/test-resources resource1 resource2 resource3 ...
Instructions
- Parse the resource names from the arguments: $ARGUMENTS
- For EACH resource, spawn a terraform-test-developer agent in PARALLEL (all Task calls in ONE message)
- Each agent should:
- First invoke Skill(terraform-provider-testing)
- Read the resource at internal/provider/{resource}_resource.go
- Create comprehensive tests at internal/provider/{resource}_resource_test.go
- Run tests and report results
Agent Prompt Template
For each resource, use this prompt:
Develop and run acceptance tests for the {resource_name} resource in this Terraform provider.
FIRST: Invoke Skill(terraform-provider-testing) to load all testing patterns and standards.
THEN:
1. Read internal/provider/{resource_name}_resource.go to understand the schema
2. Check if internal/provider/{resource_name}_resource_test.go exists
3. If exists, review and enhance; if not, create new test file
4. Implement these test functions using modern assertion patterns:
- TestAcc{PascalCaseName}Resource_basic
- TestAcc{PascalCaseName}Resource_update (if applicable)
- Import test step within _basic
5. Use custom namespace (f5xc_namespace.test), NOT system namespace
6. Use ConfigPlanChecks and ConfigStateChecks with knownvalue assertions
7. Run: TF_ACC=1 go test -v -timeout 15m -run "TestAcc{PascalCaseName}" ./internal/provider/...
8. Report results including any failures and their root causes
IMPORTANT: If tests fail due to schema or generator issues, identify the root cause but do NOT skip tests.
Parallel Execution
CRITICAL: Spawn ALL agents in a SINGLE message to maximize parallelism.
Example for 3 resources:
- Task 1: terraform-test-developer for namespace_resource
- Task 2: terraform-test-developer for healthcheck_resource
- Task 3: terraform-test-developer for origin_pool_resource
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.
- 11d ago First seen · 64 lines · 0 tokens per session scan A ce5bb4723a72
test-resources is a command published in the GitHub repository robinmordasiewicz/terraform-provider-f5xc (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.