terragrunt-workflows

terragrunt-workflows is a skill for Claude Code from Goodsmileduck/claude-registry. It costs 145 tokens per session (4,094 once invoked), scanned B, original, MIT.

A guide to Terragrunt, a tool that organises Terraform configurations and their shared infrastructure state. It covers command changes, configuration merging, dependencies, hooks, and stack files that generate infrastructure units.

In plain words
What is it for?
Use it to migrate old Terragrunt commands, understand includes and deep-merged inputs, wire dependencies and mock outputs, review run-all or stack operations, and debug hooks.
Why use it?
It helps explain changed or failing Terragrunt commands and unexpected values passed between configurations. It also adds safety guidance for planning and applying changes across multiple units.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is config_path = "../vpc".

Part of the iac-skills plugin — 3 skills shipped together

Good fit Use it to migrate old Terragrunt commands, understand includes and deep-merged inputs, wire dependencies and mock outputs, review run-all or stack operations, and debug hooks.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Goodsmileduck/claude-registry
agentmods
npx agentmods add skills/goodsmileduck/claude-registry/terragrunt-workflows

Made for: Claude Code.

Or install iac-skills, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for terragrunt-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/terragrunt-workflows/github.svg)](https://agentmods.dev/skills/goodsmileduck/claude-registry/terragrunt-workflows)
Your own site
<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/terragrunt-workflows"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/terragrunt-workflows/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.

agentmods 80×15 button for terragrunt-workflows

Your own site · 80×15
<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/terragrunt-workflows"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/terragrunt-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 145 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,094 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00145 $0.04094
Opus 5 $0.00072 $0.02047
Sonnet 5 $0.00029 $0.00819
Haiku 4.5 $0.00015 $0.00409

Measured 10d ago against content hash 0a4fbad17593, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

terragrunt-workflows scanned grade B with 2 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 10d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

execute = ["bash", "-c", "curl -X POST $SLACK_WEBHOOK -d '{\"text\":\"apply failed\"}'"]

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

execute = ["bash", "-c", "curl -X POST $SLACK_WEBHOOK -d '{\"text\":\"apply failed\"}'"]
plugins/iac-skills/skills/terragrunt-workflows/SKILL.md · 350 lines

How it starts

The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Terragrunt Workflows

Terragrunt-specific orchestration. Pairs with the terraform-workflows skill — its cross-cutting rules apply on top of this skill's. See Cross-skill notes for the exact boundary.

When to invoke

Symptoms:

  • A command that worked last quarter now warns or fails: --terragrunt-* flag deprecated, run-all deprecated, "unknown command" for what used to be terragrunt plan.
  • An include block isn't producing the merged config you expected.
  • A child unit's inputs map seems to keep parent keys you tried to drop.
  • A dependency block's mock_outputs produces values the actual upstream never emits.
  • terragrunt run --all apply is on the table for a production rollout.
  • A terragrunt.stack.hcl file is in the repo and you need to know how it generates units.
  • Hooks (before_hook, after_hook, error_hook) fire at the wrong moment or silently swallow errors.

Cross-cutting rules

These layer on top of terraform-workflows cross-cutting rules. Plan-then-apply, never bump pins in passing, never -auto-approve on shared state — all of those still apply.

  1. Treat the CLI redesign as the default. Even if a repo still uses run-all and --terragrunt-* flags, write new code in the new form (run --all, --<flag>, TG_* env vars). Set TG_STRICT_CONTROL=cli-redesign locally so you can't accidentally regress.
  2. run --all <mutation> requires a plan-aggregation step. It does NOT produce a unified plan. Without aggregation, blast radius is invisible until mid-pipeline. See run --all safety.
  3. Never edit a generated file. Files inside .terragrunt-cache/ and .terragrunt-stack/ are derived. Editing them produces drift that vanishes on the next run.
  4. Hooks run on every invocation. A before_hook with commands = ["plan", "apply"] runs both during plan and apply. If a hook performs auth refresh or state pre-fetch, it costs that work twice on a plan→apply cycle. Scope hooks tightly.
  5. mock_outputs are placeholders for plan-time, not stand-ins for unapplied state. If a plan contains a recognizable mock literal where you'd expect a real ID, the upstream dependency hasn't been applied. Apply it; do not adjust the mock to match reality.

Read the full file on GitHub · 350 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 10d ago First seen · 350 lines · 145 tokens per session scan B 0a4fbad17593

Subscribe to this mod's changes

terragrunt-workflows is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 4,094 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.