How do I install the Terragrunt 1 1 skill?

Run npx skillmds@latest add cedws/terragrunt-1-1 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Terragrunt 1 1 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Terragrunt 1 1?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Terragrunt 1 1 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Terragrunt 1 1?

cedws (@cedws) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Terragrunt 1 1 by cedws — Agent Skill

Name: Terragrunt 1 1
Author: cedws

File contents

Terragrunt 1.1

This overview applies to target Terragrunt versions of at least 1.1.

Completed experiments

Completed experiments: stack-dependencies, cas, catalog-redesign, mark-many-as-read, opt-out-auth, and dag-queue-display graduated and are enabled by default. Their former --experiment or TG_EXPERIMENT values are unnecessary and emit completed-experiment warnings.

Stacks and autoincludes

A unit or nested stack block can contain autoinclude, producing terragrunt.autoinclude.hcl beside generated configuration. References such as unit.vpc.path and stack.platform.path resolve generated paths, allowing stack-level dependency wiring and configuration patches.

Stack files accept include blocks. A unit dependency can target a stack directory and expand to its units; stacks cannot depend on units or other stacks.

Content-addressable sources

CAS is enabled by default for Git, HTTP, S3, GCS, Mercurial, SMB, and tfr:// sources. --no-cas or TG_NO_CAS=true opts out.

The update_source_with_cas = true attribute on unit, stack, or terraform rewrites relative sources into portable cas:: references during stack generation. The terraform.mutable = true attribute copies cached content into a writable working tree instead of using read-only hard links.

Discovery and catalogues

The redesigned catalog discovers components anywhere in repositories, honours .terragrunt-catalog-ignore, recognises component kinds and README metadata, and supports interactive scaffolding.

Local module source files are automatically tracked as reads. mark_glob_as_read() records additional matching files, with traversal bounded by the Git root by default and an optional --terragrunt-boundary=<path> function argument.

The --no-discovery-auth-provider-cmd flag, or TG_NO_DISCOVERY_AUTH_PROVIDER_CMD, skips authentication during discovery while retaining it for executed units. Configurations needing credentials during parsing are incompatible with that optimisation.

Multi-unit run queues display as dependency trees by default.

Release integrity

Terragrunt 1.1 began immutable GitHub releases. The install script verifies release attestations when authenticated GitHub CLI 2.81.0 or later is available; --no-verify-attestation opts out.

---name: terragrunt-1-1description: Apply Terragrunt 1.1 HCL, CLI, orchestration, migration, and behaviour changes. Load for Terragrunt work targeting 1.1 or later when the model's knowledge may predate the 2026-07-01 release.---# Terragrunt 1.1This overview applies to target Terragrunt versions of at least 1.1.## Completed experimentsCompleted experiments: `stack-dependencies`, `cas`, `catalog-redesign`, `mark-many-as-read`, `opt-out-auth`, and `dag-queue-display` graduated and are enabled by default. Their former `--experiment` or `TG_EXPERIMENT` values are unnecessary and emit completed-experiment warnings.## Stacks and autoincludesA `unit` or nested `stack` block can contain `autoinclude`, producing `terragrunt.autoinclude.hcl` beside generated configuration. References such as `unit.vpc.path` and `stack.platform.path` resolve generated paths, allowing stack-level dependency wiring and configuration patches.Stack files accept `include` blocks. A unit dependency can target a stack directory and expand to its units; stacks cannot depend on units or other stacks.## Content-addressable sourcesCAS is enabled by default for Git, HTTP, S3, GCS, Mercurial, SMB, and `tfr://` sources. `--no-cas` or `TG_NO_CAS=true` opts out.The `update_source_with_cas = true` attribute on `unit`, `stack`, or `terraform` rewrites relative sources into portable `cas::` references during stack generation. The `terraform.mutable = true` attribute copies cached content into a writable working tree instead of using read-only hard links.## Discovery and cataloguesThe redesigned `catalog` discovers components anywhere in repositories, honours `.terragrunt-catalog-ignore`, recognises component kinds and README metadata, and supports interactive scaffolding.Local module source files are automatically tracked as reads. `mark_glob_as_read()` records additional matching files, with traversal bounded by the Git root by default and an optional `--terragrunt-boundary=<path>` function argument.The `--no-discovery-auth-provider-cmd` flag, or `TG_NO_DISCOVERY_AUTH_PROVIDER_CMD`, skips authentication during discovery while retaining it for executed units. Configurations needing credentials during parsing are incompatible with that optimisation.Multi-unit run queues display as dependency trees by default.## Release integrityTerragrunt 1.1 began immutable GitHub releases. The install script verifies release attestations when authenticated GitHub CLI 2.81.0 or later is available; `--no-verify-attestation` opts out.

Frequently asked questions

Terragrunt 1 1