Agent skill · Audited from source
run-acceptance-tests
skill · hashicorp/agent-skillsMPL-2.0 licenceAudited 28 Oct 2026 · source 7e824811cd58
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 7e824811cd58 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`, when a test fails with missing environment variables, or when…
Cite
Cite this page
ModelsAtlas. “run-acceptance-tests (hashicorp/agent-skills)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/hashicorp/run-acceptance-tests
Trust audit
Audit 0.4.1 · source read 28 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 7e824811cd58 · 28 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherhashicorp GitHub organizationOwner of the repository this skill is read from
- Source folderhashicorp/agent-skills/plugins/terraform/skills/run-acceptance-testsThe exact folder we audited
- LicenceMPL-2.0As the repository states it
- Commit pinned for this verdict7e824811cd58A new audit runs when the source changes
- Repository statusNot archivedLast push 23 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`, when a test fails with missing environment variables, or when…
---
name: run-acceptance-tests
description: Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`, when a test fails with missing environment variables, or when diagnosing a failing or suspiciously passing acceptance test.
license: MPL-2.0
metadata:
lifecycle-status: active
copyright: Copyright IBM Corp. 2026
version: "0.0.1"
---
An acceptance test is a Go test function with the prefix `TestAcc`.
Before running: acceptance tests create **real infrastructure** against the
provider's live API, which may incur cost. Confirm the configured
credentials point at a test account before proceeding.
To run a focused acceptance test named `TestAccFeatureHappyPath`:
1. Run `go test -run=TestAccFeatureHappyPath -timeout 60m` with the
following environment variables:
- `TF_ACC=1`
Default to non-verbose test output. Always pass an explicit `-timeout`:
`go test` kills any test run after 10 minutes by default, and acceptance
tests routinely exceed that.
1. The acceptance tests may require additional environment variables for
specific providers. To discover which ones:
- Read the test's `PreCheck` / `testAccPreCheck` function and search the
test files: `grep -rn "os.Getenv" --include="*_test.go"`.
- Check the repository's README, CONTRIBUTING, or `.env.example` for
documented test setup.
- The provider's `Configure` method shows how credentials are resolved;
use the `provider-configuration` skill (if available) to understand a
credential provider chain.
Set the variables for the single test invocation
(`EXAMPLE_API_KEY=... TF_ACC=1 go test ...`) rather than exporting them
into the shell profile, and never write secret values into files inside
the repository.
To diagnose a failing acceptance test, use these options, in order. These
options are cumulative: each option includes all the options above it.
1. Run the test again. Use the `-count=1` option to ensure that `go test` does
not use a cached result.
1. Offer verbose `go test` output. Use the `-v` option.
1. Offer debug-level logging. Enable debug-level logging with the environment
variable `TF_LOG=debug`.
1. Offer to persist the acceptance test's Terraform workspace. Enable
persistence with the environment variable `TF_ACC_WORKING_DIR_PERSIST=1`.
A passing acceptance test may be a false negative. To "flip" a passing
acceptance test named `TestAccFeatureHappyPath`:
1. Edit the value of one of the TestCheckFuncs in one of the TestSteps in the
TestCase.
1. Run the acceptance test. Expect the test to fail.
1. If the test fails, then undo the edit and report a successful flip. Else,
keep the edit and report an unsuccessful flip.
If a test run is interrupted, real resources may be left behind; run the
provider's sweepers if it registers them (see the `provider-test-patterns`
skill's sweeper reference, if available). For writing or restructuring
tests, use the `provider-test-patterns` skill.Excerpt, first 3,058 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 7e82481
git clone https://github.com/hashicorp/agent-skills git -C agent-skills checkout 7e824811cd58
The author documents no install command, so this uses the repository directly. Our verdict covers commit 7e824811cd58 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
7e824811cd58
Similar skills
All testing skills →hashicorp/agent-skills
Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import…
hashicorp/agent-skills
Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations,…
hashicorp/agent-skills
Push Packer build metadata to HCP Packer registry for tracking and managing image lifecycle. Use when integrating Packer builds with HCP Packer for version control and governance.
hashicorp/agent-skills
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
hashicorp/agent-skills
Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider…
hashicorp/agent-skills
Write, test, or convert Terraform Policy files (.policy.hcl, .policytest.hcl, Sentinel→tfpolicy). Triggers: policy.hcl, policytest, convert sentinel, tfpolicy, write a policy.
Questions about run-acceptance-tests
What does the run-acceptance-tests skill do?
Is run-acceptance-tests safe to install?
What can run-acceptance-tests access on my machine?
How current is this page?
Sources
- github.com/hashicorp/agent-skills/tree/main/plugins/terraform/sk — the audited source at commit 7e824811cd58 and every finding aboveObserved · 28 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the run-acceptance-tests skill do?
- Is run-acceptance-tests safe to install?
- What can run-acceptance-tests access on my machine?