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.
npx skills add adonai-labs/agent-runway --skill iacgit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/skills/adonai-labs/agent-runway/iac)<a href="https://agentmods.dev/skills/adonai-labs/agent-runway/iac"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/iac/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/skills/adonai-labs/agent-runway/iac"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/iac.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.00090 | $0.01416 |
| Opus 5 | $0.00045 | $0.00708 |
| Sonnet 5 | $0.00018 | $0.00283 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
iac 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure as Code
Invoke Command
/iac <what you need>
Examples:
/iac new App Service + SQL Database for the orders service/iac review infra/main.bicep/iac add Key Vault and update app settings references/iac create dev and prod parameter files
Not sure which skill to use? Start with
/start- it classifies intent and routes to the right skill.
Workflow
Follow these steps in order.
Step 0 - Risk Classification and Routing Gate
Before any IaC change, classify:
- Impact: low/medium/high
- Reversibility: reversible/hard-to-reverse/irreversible
- Uncertainty: low/medium/high
- Cost of error: low/medium/high
Contrarian trigger (any true):
- impact is high and reversibility is hard-to-reverse or irreversible
- uncertainty is high
- migration/cutover with ambiguous rollback
- architecture decision with multiple viable infrastructure patterns
Execution mode:
- Execution-only: low risk + reversible + low uncertainty
- Execution+validation: medium risk or multi-resource change
- Execution+contrarian: contrarian trigger active
Policy:
- Execution-only: continue with minimal questions and minimal process overhead.
- Execution+validation: continue with normal IaC workflow.
- Execution+contrarian: run mandatory contrarian review before writing IaC.
Decision action table:
| Profile | Action |
|---|---|
| High impact + irreversible + high uncertainty | Block - stop and escalate before changes |
| Medium risk profile | Warn - continue only with explicit risk notes and validation checks |
| Low risk + reversible + low uncertainty | Execute - use short path |
Step 0.5 - Contrarian Review (Required when triggered)
When triggered, document:
- recommended infrastructure approach
- strongest counter-argument
- at least one viable alternative
- top operational/security risks and invalidation signals
- verdict:
Go,Go with conditions, orStop
If verdict is Stop, halt and escalate.
If verdict is Go with conditions, convert conditions to explicit validation checks.
What ships with it
2 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.
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.
- 10d ago First seen · 187 lines · 90 tokens per session scan A 6d880a453d3a
iac is a skill published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 20d ago), licensed MIT. It adds 90 tokens to every session and 1,416 once invoked, about $0.0005 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.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
project-check
Existing project health scan — audits Infrastructure, Security, Quality, and Harness setup. Read-only. Use when: '/project-check', 'project health check', 'project audit', 'what\'s missing', 'analyze my project', 'check setup'. Ends with /project-init and /setup recommendations. NOT for new projects (use…