A command for applying Infrastructure as Code (configuration files that create and change cloud infrastructure). It previews the planned changes, asks for confirmation, and requires extra confirmation for destructive changes.

Use it when you intentionally need to apply an infrastructure plan and review its additions, changes, and deletions first.

It reduces the risk of changing or deleting real cloud resources accidentally by showing the plan before applying it.

nyann:apply — Command by thettwe

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/thettwe/nyann/apply

Clone the repo

git clone --depth 1 https://github.com/thettwe/nyann

Per session 85 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 795 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00085	$0.00795
Opus 5	$0.00043	$0.00398
Sonnet 5	$0.00017	$0.00159
Haiku 4.5	$0.00009	$0.00080

Measured 2d ago against content hash b18cc44ae55e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nyann:apply 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 2d 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.

commands/apply.md · 65 lines

What it actually says

Plugin root: This is a Claude Code plugin, NOT a CLI tool. Do NOT search via which, npm list, pip list, or brew list. This file is at <plugin_root>/commands/. All scripts: <plugin_root>/bin/. Read the matching skills/*/SKILL.md for the full flow.

/nyann:apply

Wraps bin/iac-apply.sh. Highest-stakes mutator — can change real cloud infrastructure. Apply is NEVER the default. Flow:

Confirm IaC apply intent + an infra signal (not "apply a patch").
Preview first: bin/iac-apply.sh --target <cwd> [--unit <path>] (no --apply) → status:"preview", mutates nothing. Show the add/change/destroy summary.
Confirm with the user. AskUserQuestion is MANDATORY on a destructive plan (any destroy > 0, or any advisory plan).
Apply: add --apply (and --confirm-destroy --confirmed ONLY after the user confirms a destroy).

Gate ladder (enforced in the script): plan obtained first → Gate 1 preview-by-default (no --apply or any --dry-run → preview; --dry-run beats --apply) → Gate 2 destructive confirmation (destructive plan passes only with --confirm-destroy true AND --confirmed true, else refused) → Gate 3 CLI presence (absent → skipped) → execute (tool output goes to your terminal, never captured) → write an IacApplyRecord (metadata only — no secrets/state).

`.status`	Meaning
`applied`	Apply ran — read `.exit_code`; see `.record_path`.
`preview`	No `--apply` (or `--dry-run`) — nothing applied.
`refused`	A gate blocked it (e.g. unconfirmed destroy). Exit 1.
`skipped`	CLI/backend/creds absent. Exit 0. Nothing applied.

See skills/iac-apply/SKILL.md for the full gate ladder and the DISAMBIGUATION that keeps /nyann:apply off the generic word "apply". To only preview → /nyann:plan.

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.

2d ago First seen · 65 lines · 85 tokens per session scan A b18cc44ae55e

Subscribe to this mod's changes

nyann:apply is a command published in the GitHub repository thettwe/nyann (6 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 795 once invoked, about $0.0004 per session on Opus 5. 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.

Code review Planning claude-code claude-code-plugin claude-skills github governance scaffolding

nyann:apply

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/nyann:apply

What this file has done since we first saw it

Other commands, from other repositories

create-namespace

oss

setup-oss

forge

run-tests

optimize-costs