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.
git clone --depth 1 https://github.com/thettwe/nyannWrote 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.
[](https://agentmods.dev/commands/thettwe/nyann/apply)<a href="https://agentmods.dev/commands/thettwe/nyann/apply"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/apply/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.
<a href="https://agentmods.dev/commands/thettwe/nyann/apply"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/apply.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00085 | $0.00795 |
| Opus 5.5 | $0.00034 | $0.00318 |
| Sonnet 5.5 | $0.00017 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00080 |
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 1mo 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.
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 --confirmedONLY 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.
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.
- 1mo ago First seen · 65 lines · 85 tokens per session scan A b18cc44ae55e
nyann:apply is a command published in the GitHub repository thettwe/nyann (7 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 795 once invoked, about $0.0003 per session on Opus 5.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.
Other commands, from other repositories
well-architected
Six-pillar well-architected review with scores and improvement roadmap.
disaster-recovery
Design disaster recovery strategy with RTO/RPO targets, backup config, and incident runbooks.
eu-cloud-sovereignty
You are helping an enterprise architect generate an EU Cloud Sovereignty Framework Assessment for an organisation procuring, specifying, or evaluating cloud services against the European Commission's EU Cloud Sovereignty Framework (v1.2.1, October 2025). The framework supplements security assurance (SecNumCloud, EUCS…
gcp-research
Research Google Cloud services and architecture patterns using Google Developer Knowledge MCP for authoritative guidance.
finops
Create FinOps strategy with cloud cost management, optimization, governance, and forecasting.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.