---
title: "Terraform module refactor: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/hashicorp-refactor-module/
description: "Extract Terraform modules while explicitly migrating existing state addresses."
---

# Terraform module refactor: review, setup & limitations · Undominated.ai

> Extract Terraform modules while explicitly migrating existing state addresses.

[← Explore all skills](/skills/)

INFRASTRUCTURE DEVELOPMENT / HashiCorp

# Terraform module refactor

Extract Terraform modules while explicitly migrating existing state addresses.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/hashicorp/agent-skills/tree/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher HashiCorp
 Licence [MPL-2.0 ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE)
 Revision f706481af9b8
 [Read what was—and wasn’t—checked ↓](#review)

“Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.”

 [HashiCorp · upstream description ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The definition prefers state list/show-json over treating raw state format as a stable interface and distinguishes moved blocks from manual state migration.
- Split a monolithic configuration without unintentionally recreating managed resources.

### A good fit for

 - Split a monolithic configuration without unintentionally recreating managed resources.
- Choose module boundaries from resource lifecycle coupling before moving state addresses.

### Weigh up before choosing

 - State contains plaintext sensitive values even in JSON output. Terraform tests defaulting to apply can create real infrastructure; address migration requires a reviewed plan and recoverable state.
- Source inspection only; no installation, authenticated operation, runtime benchmark or security certification was performed.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/terraform/skills/refactor-module/SKILL.md
- LICENSE
- README.md
- SKILLS.md

### Our findings

 - The definition prefers state list/show-json over treating raw state format as a stable interface and distinguishes moved blocks from manual state migration.
- The encapsulation guidance groups resources sharing a lifecycle and keeps resources with different lifecycles outside the same module boundary.

### Not established by this review

 - Third-party instructions and helpers were not executed; service access, host compatibility and outcomes remain untested.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md)

DOCUMENTED COMMAND

 npx skills add hashicorp/agent-skills/plugins/terraform/skills/refactor-module Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 - The README says to install one skill from its path and points at SKILLS.md. That file lists plugins/terraform/skills/refactor-module as active.
- The documented command does not pin revision f706481af9b8fedb66de909f6243ad29601afa0c. Inspect the installed file against that revision before use.
- Do not run state mv or apply until the plan and the state addresses have been reviewed. Do not print state.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/hashicorp-refactor-module/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision f706481a, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named refactor-module. Keep SKILL.md and the licence together.

### Before you start

 - Node.js and npm for the documented Skills installer
- Terraform and permission to read state only when planning a migration

### Compatibility

Agent Skills-compatible hosts · Terraform

### Local instructions with workflow-dependent access

 - Reads sensitive state and changes configuration; state moves and apply-mode checks can alter live infrastructure.

### Cost model

Skill source is freely available under its stated licence; host, infrastructure and service usage may incur charges.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/skills/hashicorp-refactor-module/bundle.zip)[Raw Markdown ↗](/resources/skills/hashicorp-refactor-module/definition.md)
 ---
name: refactor-module
description: Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
metadata:
 lifecycle-status: active
 copyright: Copyright IBM Corp. 2026
 version: "0.0.1"
---

# Skill: Refactor Module

## Overview
This skill guides AI agents in transforming monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

## Capability Statement
The agent will analyze existing Terraform code and systematically refactor it into well-structured modules with:
- Clear interface contracts (variables and outputs)
- Proper encapsulation and abstraction
- Versioning and documentation
- Testing frameworks
- Migration path for existing state

## Prerequisites
- Existing Terraform configuration to refactor
- Understanding of resource dependencies
- Access to inspect current state via `terraform state list` / `terraform show -json` (for migration planning)
- Knowledge of module registry patterns

## Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `source_directory` | string | Yes | Path to existing Terraform configuration |
| `module_name` | string | Yes | Name for the new module |
| `abstraction_level` | string | No | "simple", "intermediate", "advanced" (default: intermediate) |
| `preserve_state` | boolean | Yes | Whether to maintain state compatibility |
| `target_registry` | string | No | Target module registry (local, private, public) |

## Execution Steps

### 1. Analysis Phase
```markdown
**Identify Refactoring Candidates**
- Group resources by logical function
- Identify repeated patterns
- Map resource dependencies
- Detect configuration coupling
- Analyze variable usage patterns

**Complexity Assessment**
- Count resource relationships
- Measure variable propagation depth
- Identify cross-resource references
- Evaluate state migration complexity
```

### 2. Module Design

#### Interface Design
```hcl
# Define clear input contract
variable "network_config" {
 description = "Network configuration parameters"
 type = object({
 cidr_block = string
 availability_zones = list(string)
 enable_nat = bool
 })

 validation {
 condition = can(cidrhost(var.network_config.cidr_block, 0))
 error_message = "CIDR block must be valid IPv4 CIDR."
 }
}

# Define output contract
output "vpc_id" {
 description = "ID of the created VPC"
 value = aws_vpc.main.id
}

output "private_subnet_ids" {
 description = "List of private subnet IDs"
 value = { for k, v in aws_subnet.private : k => v.id }
}
```

#### Encapsulation Strategy
```markdown
**What to Include in Module:**
- Tightly coupled resources (VPC + subnets)
- Resources with shared lifecycle
- Configuration with clear boundaries

**What to Keep Separate:**
- Cross-cutting concerns (monitoring, tagging)
- Resources with different lifecycles
- Provider-specific configurations
```

### 3. Code Transformation

#### Before: Monolithic Configuration
```hcl
# main.tf (monolithic)
resource "aws_vpc" "main" {
 cidr_block = "10.0.0.0/16"
 enable_dns_hostnames = true

 tags = {
 Name = "production-vpc"
 Environment = "prod"
 }
}

resource "aws_subnet" "public_1" {
 vpc_id = aws_vpc.main.id
 cidr_block = "10.0.1.0/24"
 availability_zone = "us-east-1a"

 tags = {
 Name = "public-subnet-1"
 Type = "public"
 }
}

resource "aws_subnet" "public_2" {
 vpc_id = aws_vpc.main.id
 cidr_block = "10.0.2.0/24"
 availability_zone = "us-east-1b"

 tags = {
 Name = "public-subnet-2"
 Type = "public"
 }
}

resource "aws_internet_gateway" "main" {
 vpc_id = aws_vpc.main.id

 tags = {
 Name = "production-igw"
 }
}

# ... more repetitive subnet and routing resources
```

#### After: Modular Structure
```hcl
# modules/vpc/main.tf
locals {
 subnet_count = length(var.availability_zones)
}

resource "aws_vpc" "main" {
 cidr_block = var.cidr_block
 enable_dns_hostnames = var.enable_dns_hostnames
 enable_dns_support = var.enable_dns_support

 tags = merge(
 var.tags,
 {
 Name = var.name
 }
 )
}

resource "aws_subnet" "public" {
 for_each = var.create_public_subnets ? toset(var.availability_zones) : []

 vpc_id = aws_vpc.main.id
 cidr_block = cidrsubnet(var.cidr_block, 8, index(var.availability_zones, each.value))
 availability_zone = each.value
 map_public_ip_on_launch = true

 tags = merge(
 var.tags,
 {
 Name = "${var.name}-public-${each.value}"
 Type = "public"
 }
 )
}

resource "aws_internet_gateway" "main" {
 count = var.create_public_subnets ? 1 : 0
 vpc_id = aws_vpc.main.id

 tags = merge(
 var.tags,
 {
 Name = "${var.name}-igw"
 }
 )
}

# modules/vpc/variables.tf
variable "name" {
 description = "Name prefix for all resources"
 type = string
}

variable "cidr_block" {
 description = "CIDR block for the VPC"
 type = string

 validation {
 condition = can(cidrhost(var.cidr_block, 0))
 error_message = "Must be a valid IPv4 CIDR block."
 }
}

variable "availability_zones" {
 description = "List of availability zones"
 type = list(string)
}

variable "create_public_subnets" {
 description = "Whether to create public subnets"
 type = bool
 default = true
}

variable "enable_dns_hostnames" {
 description = "Enable DNS hostnames in the VPC"
 type = bool
 default = true
}

variable "enable_dns_support" {
 description = "Enable DNS support in the VPC"
 type = bool
 default = true
}

variable "tags" {
 description = "Tags to apply to all resources"
 type = map(string)
 default = {}
}

# modules/vpc/outputs.tf
output "vpc_id" {
 description = "ID of the VPC"
 value = aws_vpc.main.id
}

output "vpc_cidr_block" {
 description = "CIDR block of the VPC"
 value = aws_vpc.main.cidr_block
}

output "public_subnet_ids" {
 description = "Map of availability zones to public subnet IDs"
 value = { for k, v in aws_subnet.public : k => v.id }
}

output "internet_gateway_id" {
 description = "ID of the internet gateway"
 value = try(aws_internet_gateway.main[0].id, null)
}

# Root configuration using module
module "vpc" {
 source = "./modules/vpc"

 name = "production"
 cidr_block = "10.0.0.0/16"
 availability_zones = ["us-east-1a", "us-east-1b", "us-east-1c"]

 tags = {
 Environment = "production"
 ManagedBy = "Terraform"
 }
}
```

### 4. State Migration

#### Inspecting Current State
Before writing `moved` blocks or `state mv` commands, inspect the current state to map
existing resource addresses. Prefer the documented, stable, and more token-efficient
commands over reading the raw state file:

```bash
# Enumerate current resource addresses (the inputs for `moved` / `state mv`)
terraform state list

# Inspect resolved attribute values when you need them
terraform show -json | jq '.values.root_module'
```

`terraform show -json` requires providers to be installed (`terraform init`), since it
renders values against provider schemas. **Fall back to the raw state
(`terraform state pull` / `terraform.tfstate`) only when** providers aren't available and
`init` can't run, you need only coarse info (addresses, outputs, `serial`/`lineage`), or you
must avoid executing Terraform. Avoid parsing the raw version-4 state format as a stable
interface. **Note:** state contains sensitive values in plaintext in every format — never
echo state contents into logs or output.

#### Generate Migration Plan
```hcl
# migration.tf
# Use moved blocks for state refactoring (Terraform 1.1+)

moved {
 from = aws_vpc.main
 to = module.vpc.aws_vpc.main
}

moved {
 from = aws_subnet.public_1
 to = module.vpc.aws_subnet.public["us-east-1a"]
}

moved {
 from = aws_subnet.public_2
 to = module.vpc.aws_subnet.public["us-east-1b"]
}

moved {
 from = aws_internet_gateway.main
 to = module.vpc.aws_internet_gateway.main[0]
}
```

#### Manual State Migration (Pre-1.1)
```bash
# Generate state migration commands
terraform state mv aws_vpc.main module.vpc.aws_vpc.main
terraform state mv aws_subnet.public_1 'module.vpc.aws_subnet.public["us-east-1a"]'
terraform state mv aws_subnet.public_2 'module.vpc.aws_subnet.public["us-east-1b"]'
terraform state mv aws_internet_gateway.main 'module.vpc.aws_internet_gateway.main[0]'
```

### 5. Module Documentation

```markdown
# VPC Module

## Overview
Creates a VPC with configurable public and private subnets across multiple availability zones.

## Features
- Multi-AZ subnet deployment
- Optional NAT gateway configuration
- VPC Flow Logs integration
- Customizable CIDR allocation

## Usage

\`\`\`hcl
module "vpc" {
 source = "./modules/vpc"

 name = "my-vpc"
 cidr_block = "10.0.0.0/16"
 availability_zones = ["us-east-1a", "us-east-1b"]

 create_public_subnets = true
 create_private_subnets = true
 enable_nat_gateway = true

 tags = {
 Environment = "production"
 }
}
\`\`\`

## Requirements

| Name | Version |
|------|---------|
| terraform | >= 1.5.0 |
| aws | ~> 5.0 |

## Inputs

| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
| name | Name prefix for resources | `string` | n/a | yes |
| cidr_block | VPC CIDR block | `string` | n/a | yes |
| availability_zones | List of AZs | `list(string)` | n/a | yes |

## Outputs

| Name | Description |
|------|-------------|
| vpc_id | VPC identifier |
| public_subnet_ids | Map of public subnet IDs |
| private_subnet_ids | Map of private subnet IDs |

## Examples

See [examples/](./examples/) directory for complete usage examples.
```

### 6. Testing

Use skill terraform-test

**Test File**: A `.tftest.hcl` or `.tftest.json` file containing test configuration and run blocks that validate your Terraform configuration.

**Test Block**: Optional configuration block that defines test-wide settings (available since Terraform 1.6.0).

**Run Block**: Defines a single test scenario with optional variables, provider configurations, and assertions. Each test file requires at least one run block.

**Assert Block**: Contains conditions that must evaluate to true for the test to pass. Failed assertions cause the test to fail.

**Mock Provider**: Simulates provider behavior without creating real infrastructure (available since Terraform 1.7.0).

**Test Modes**: Tests run in apply mode (default, creates real infrastructure) or plan mode (validates logic without creating resources).

#### File Structure

Terraform test files use the `.tftest.hcl` or `.tftest.json` extension and are typically organized in a `tests/` directory. Use clear naming conventions to distinguish between unit tests (plan mode) and integration tests (apply mode):

```
my-module/
├── main.tf
├── variables.tf
├── outputs.tf
└── tests/
 ├── unit_test.tftest.hcl # Unit test (plan mode)
 └── integration_test.tftest.hcl # Integration test (apply mode - creates real resources)
```

## Refactoring Patterns

### Pattern 1: Resource Grouping
Extract related resources into cohesive modules:
- Networking (VPC, Subnets, Route Tables)
- Compute (ASG, Launch Templates, Load Balancers)
- Data (RDS, ElastiCache, S3)

### Pattern 2: Configuration Layering
```hcl
# Base module with defaults
module "vpc_base" {
 source = "./modules/vpc-base"
 # Minimal required inputs
}

# Environment-specific wrapper
module "vpc_prod" {
 source = "./modules/vpc-production"
 # Inherits from base, adds prod-specific config
}
```

### Pattern 3: Composition
```hcl
# Small, focused modules
module "vpc" {
 source = "./modules/vpc"
}

module "security_groups" {
 source = "./modules/security-groups"
 vpc_id = module.vpc.vpc_id
}

module "application" {
 source = "./modules/application"
 vpc_id = module.vpc.vpc_id
 subnet_ids = module.vpc.private_subnet_ids
 sg_ids = module.security_groups.app_sg_ids
}
```

## Common Pitfalls

### 1. Over-Abstraction
```hcl
# ❌ Don't create overly generic modules
variable "resources" {
 type = map(map(any)) # Too flexible, hard to validate
}

# ✅ Do use specific, typed interfaces
variable "database_config" {
 type = object({
 engine = string
 instance_class = string
 })
}
```

### 2. Tight Coupling
```hcl
# ❌ Don't couple modules through direct references
# module A
output "instance_id" { value = aws_instance.app.id }

# module B (in same config)
resource "aws_eip" "app" {
 instance = module.a.instance_id # Tight coupling
}

# ✅ Do pass dependencies through root module
module "compute" {
 source = "./modules/compute"
}

resource "aws_eip" "app" {
 instance = module.compute.instance_id
}
```

### 3. State Migration Errors
Always test migration in non-production first:
```bash
# Create plan to verify no changes after migration
terraform plan -out=migration.tfplan

# Review carefully
terraform show migration.tfplan

# Apply only if plan shows no changes
terraform apply migration.tfplan
```

## Version Control Strategy

```hcl
# Use semantic versioning for modules
module "vpc" {
 source = "git::https://github.com/org/terraform-modules.git//vpc?ref=v1.2.0"
 version = "~> 1.2"
}

# Pin to specific versions in production
# Use version ranges in development
```

## Success Criteria

- [ ] Module has single, well-defined responsibility
- [ ] All variables have descriptions and types
- [ ] Validation rules prevent invalid configurations
- [ ] Outputs provide sufficient information for consumers
- [ ] Documentation includes usage examples
- [ ] Tests verify module behavior
- [ ] State migration completed without resource recreation
- [ ] No plan differences after refactoring

## Related Skills
- [Terraform code generation](https://raw.githubusercontent.com/hashicorp/agent-skills/refs/heads/main/plugins/terraform/skills/terraform-style-guide/SKILL.md) - Style guide for the new Terraform Module
- [Azure Verified Modules](https://raw.githubusercontent.com/hashicorp/agent-skills/refs/heads/main/plugins/terraform/skills/azure-verified-modules/SKILL.md) - Recommended module specifications for Azure

## Resources
- [Terraform Module Development](https://developer.hashicorp.com/terraform/language/modules/develop)
- [Module Best Practices](https://developer.hashicorp.com/terraform/cloud-docs/registry/design)

## Revision History

| Version | Date | Changes |
|---------|------|---------|
| 1.0.0 | 2025-11-07 | Initial skill definition |

The download contains SKILL.md . Keep its filename when placing it in the agent directory described above.

By **HashiCorp**. [Exact upstream source ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md) · [Licence](/resources/skills/hashicorp-refactor-module/LICENSE.txt) · [Attribution](/resources/skills/hashicorp-refactor-module/ATTRIBUTION.txt)

SHA-256 da0b9f3599ed0e513a92b57f0c0ff3fad3168ba461215a9197ebbffe4e0d538f

 Read the applicable licence Mozilla Public License Version 2.0
==================================

1. Definitions
--------------

1.1. "Contributor"
 means each individual or legal entity that creates, contributes to
 the creation of, or owns Covered Software.

1.2. "Contributor Version"
 means the combination of the Contributions of others (if any) used
 by a Contributor and that particular Contributor's Contribution.

1.3. "Contribution"
 means Covered Software of a particular Contributor.

1.4. "Covered Software"
 means Source Code Form to which the initial Contributor has attached
 the notice in Exhibit A, the Executable Form of such Source Code
 Form, and Modifications of such Source Code Form, in each case
 including portions thereof.

1.5. "Incompatible With Secondary Licenses"
 means

 (a) that the initial Contributor has attached the notice described
 in Exhibit B to the Covered Software; or

 (b) that the Covered Software was made available under the terms of
 version 1.1 or earlier of the License, but not also under the
 terms of a Secondary License.

1.6. "Executable Form"
 means any form of the work other than Source Code Form.

1.7. "Larger Work"
 means a work that combines Covered Software with other material, in
 a separate file or files, that is not Covered Software.

1.8. "License"
 means this document.

1.9. "Licensable"
 means having the right to grant, to the maximum extent possible,
 whether at the time of the initial grant or subsequently, any and
 all of the rights conveyed by this License.

1.10. "Modifications"
 means any of the following:

 (a) any file in Source Code Form that results from an addition to,
 deletion from, or modification of the contents of Covered
 Software; or

 (b) any new file in Source Code Form that contains any Covered
 Software.

1.11. "Patent Claims" of a Contributor
 means any patent claim(s), including without limitation, method,
 process, and apparatus claims, in any patent Licensable by such
 Contributor that would be infringed, but for the grant of the
 License, by the making, using, selling, offering for sale, having
 made, import, or transfer of either its Contributions or its
 Contributor Version.

1.12. "Secondary License"
 means either the GNU General Public License, Version 2.0, the GNU
 Lesser General Public License, Version 2.1, the GNU Affero General
 Public License, Version 3.0, or any later versions of those
 licenses.

1.13. "Source Code Form"
 means the form of the work preferred for making modifications.

1.14. "You" (or "Your")
 means an individual or a legal entity exercising rights under this
 License. For legal entities, "You" includes any entity that
 controls, is controlled by, or is under common control with You. For
 purposes of this definition, "control" means (a) the power, direct
 or indirect, to cause the direction or management of such entity,
 whether by contract or otherwise, or (b) ownership of more than
 fifty percent (50%) of the outstanding shares or beneficial
 ownership of such entity.

2. License Grants and Conditions
--------------------------------

2.1. Grants

Each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:

(a) under intellectual property rights (other than patent or trademark)
 Licensable by such Contributor to use, reproduce, make available,
 modify, display, perform, distribute, and otherwise exploit its
 Contributions, either on an unmodified basis, with Modifications, or
 as part of a Larger Work; and

(b) under Patent Claims of such Contributor to make, use, sell, offer
 for sale, have made, import, and otherwise transfer either its
 Contributions or its Contributor Version.

2.2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution
become effective for each Contribution on the date the Contributor first
distributes such Contribution.

2.3. Limitations on Grant Scope

The licenses granted in this Section 2 are the only rights granted under
this License. No additional rights or licenses will be implied from the
distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a
Contributor:

(a) for any code that a Contributor has removed from Covered Software;
 or

(b) for infringements caused by: (i) Your and any other third party's
 modifications of Covered Software, or (ii) the combination of its
 Contributions with other software (except as part of its Contributor
 Version); or

(c) under Patent Claims infringed by Covered Software in the absence of
 its Contributions.

This License does not grant any rights in the trademarks, service marks,
or logos of any Contributor (except as may be necessary to comply with
the notice requirements in Section 3.4).

2.4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to
distribute the Covered Software under a subsequent version of this
License (see Section 10.2) or under the terms of a Secondary License (if
permitted under the terms of Section 3.3).

2.5. Representation

Each Contributor represents that the Contributor believes its
Contributions are its original creation(s) or it has sufficient rights
to grant the rights to its Contributions conveyed by this License.

2.6. Fair Use

This License is not intended to limit any rights You have under
applicable copyright doctrines of fair use, fair dealing, or other
equivalents.

2.7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
in Section 2.1.

3. Responsibilities
-------------------

3.1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any
Modifications that You create or to which You contribute, must be under
the terms of this License. You must inform recipients that the Source
Code Form of the Covered Software is governed by the terms of this
License, and how they can obtain a copy of this License. You may not
attempt to alter or restrict the recipients' rights in the Source Code
Form.

3.2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

(a) such Covered Software must also be made available in Source Code
 Form, as described in Section 3.1, and You must inform recipients of
 the Executable Form how they can obtain a copy of such Source Code
 Form by reasonable means in a timely manner, at a charge no more
 than the cost of distribution to the recipient; and

(b) You may distribute such Executable Form under the terms of this
 License, or sublicense it under different terms, provided that the
 license for the Executable Form does not attempt to limit or alter
 the recipients' rights in the Source Code Form under this License.

3.3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice,
provided that You also comply with the requirements of this License for
the Covered Software. If the Larger Work is a combination of Covered
Software with a work governed by one or more Secondary Licenses, and the
Covered Software is not Incompatible With Secondary Licenses, this
License permits You to additionally distribute such Covered Software
under the terms of such Secondary License(s), so that the recipient of
the Larger Work may, at their option, further distribute the Covered
Software under the terms of either this License or such Secondary
License(s).

3.4. Notices

You may not remove or alter the substance of any license notices
(including copyright notices, patent notices, disclaimers of warranty,
or limitations of liability) contained within the Source Code Form of
the Covered Software, except that You may alter any license notices to
the extent required to remedy known factual inaccuracies.

3.5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support,
indemnity or liability obligations to one or more recipients of Covered
Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any
such warranty, support, indemnity, or liability obligation is offered by
You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support,
indemnity or liability terms You offer. You may include additional
disclaimers of warranty and limitations of liability specific to any
jurisdiction.

4. Inability to Comply Due to Statute or Regulation
---------------------------------------------------

If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Software due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description must
be placed in a text file included with all distributions of the Covered
Software under this License. Except to the extent prohibited by statute
or regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.

5. Termination
--------------

5.1. The rights granted under this License will terminate automatically
if You fail to comply with any of its terms. However, if You become
compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such
Contributor explicitly and finally terminates Your grants, and (b) on an
ongoing basis, if such Contributor fails to notify You of the
non-compliance by some reasonable means prior to 60 days after You have
come back into compliance. Moreover, Your grants from a particular
Contributor are reinstated on an ongoing basis if such Contributor
notifies You of the non-compliance by some reasonable means, this is the
first time You have received notice of non-compliance with this License
from such Contributor, and You become compliant prior to 30 days after
Your receipt of the notice.

5.2. If You initiate litigation against any entity by asserting a patent
infringement claim (excluding declaratory judgment actions,
counter-claims, and cross-claims) alleging that a Contributor Version
directly or indirectly infringes any patent, then the rights granted to
You by any and all Contributors for the Covered Software under Section
2.1 of this License shall terminate.

5.3. In the event of termination under Sections 5.1 or 5.2 above, all
end user license agreements (excluding distributors and resellers) which
have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.

************************************************************************
* *
* 6. Disclaimer of Warranty *
* ------------------------- *
* *
* Covered Software is provided under this License on an "as is" *
* basis, without warranty of any kind, either expressed, implied, or *
* statutory, including, without limitation, warranties that the *
* Covered Software is free of defects, merchantable, fit for a *
* particular purpose or non-infringing. The entire risk as to the *
* quality and performance of the Covered Software is with You. *
* Should any Covered Software prove defective in any respect, You *
* (not any Contributor) assume the cost of any necessary servicing, *
* repair, or correction. This disclaimer of warranty constitutes an *
* essential part of this License. No use of any Covered Software is *
* authorized under this License except under this disclaimer. *
* *
************************************************************************

************************************************************************
* *
* 7. Limitation of Liability *
* -------------------------- *
* *
* Under no circumstances and under no legal theory, whether tort *
* (including negligence), contract, or otherwise, shall any *
* Contributor, or anyone who distributes Covered Software as *
* permitted above, be liable to You for any direct, indirect, *
* special, incidental, or consequential damages of any character *
* including, without limitation, damages for lost profits, loss of *
* goodwill, work stoppage, computer failure or malfunction, or any *
* and all other commercial damages or losses, even if such party *
* shall have been informed of the possibility of such damages. This *
* limitation of liability shall not apply to liability for death or *
* personal injury resulting from such party's negligence to the *
* extent applicable law prohibits such limitation. Some *
* jurisdictions do not allow the exclusion or limitation of *
* incidental or consequential damages, so this exclusion and *
* limitation may not apply to You. *
* *
************************************************************************

8. Litigation
-------------

Any litigation relating to this License may be brought only in the
courts of a jurisdiction where the defendant maintains its principal
place of business and such litigation shall be governed by laws of that
jurisdiction, without reference to its conflict-of-law provisions.
Nothing in this Section shall prevent a party's ability to bring
cross-claims or counter-claims.

9. Miscellaneous
----------------

This License represents the complete agreement concerning the subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. Any law or regulation which provides
that the language of a contract shall be construed against the drafter
shall not be used to construe this License against a Contributor.

10. Versions of the License
---------------------------

10.1. New Versions

Mozilla Foundation is the license steward. Except as provided in Section
10.3, no one other than the license steward has the right to modify or
publish new versions of this License. Each version will be given a
distinguishing version number.

10.2. Effect of New Versions

You may distribute the Covered Software under the terms of the version
of the License under which You originally received the Covered Software,
or under the terms of any subsequent version published by the license
steward.

10.3. Modified Versions

If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).

10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses

If You choose to distribute Source Code Form that is Incompatible With
Secondary Licenses under the terms of this version of the License, the
notice described in Exhibit B of this License must be attached.

Exhibit A - Source Code Form License Notice
-------------------------------------------

 This Source Code Form is subject to the terms of the Mozilla Public
 License, v. 2.0. If a copy of the MPL was not distributed with this
 file, You can obtain one at https://mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.

You may add additional accurate notices of copyright ownership.

Exhibit B - "Incompatible With Secondary Licenses" Notice
---------------------------------------------------------

 This Source Code Form is "Incompatible With Secondary Licenses", as
 defined by the Mozilla Public License, v. 2.0.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned plugins/terraform/skills/refactor-module/SKILL.md ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md) Checked 2026-10-14 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md Supports: summary, review, install, access, limitations
- [Pinned LICENSE ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE) Checked 2026-10-14 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/LICENSE Supports: license
- [Pinned README.md ↗](https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md) Checked 2026-10-14 https://github.com/hashicorp/agent-skills/blob/f706481af9b8fedb66de909f6243ad29601afa0c/README.md Supports: summary, review, install, access, limitations
- [Pinned continuation review C2-W44 ↗](https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/hashicorp/agent-skills/f706481af9b8fedb66de909f6243ad29601afa0c/plugins/terraform/skills/refactor-module/SKILL.md Supports: review.findings, bestFor

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Infisical Terraform Provider ↗ Infisical skill for the Infisical Terraform provider: provider authentication, ephemeral secret reads, data sources, project roles, access approval policies and Terraform Cloud OIDC.](/skills/infisical-terraform/)[### Provider actions ↗ Guides Terraform Plugin Framework action registration, configuration and lifecycle-trigger integration.](/skills/hashicorp-provider-actions/)[### Provider configuration ↗ Builds a provider Configure method as a credential chain and names every source a failed login tried.](/skills/hashicorp-provider-configuration/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
