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 tonone-ai/tonone --skill warden-iamgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/warden-iam)<a href="https://agentmods.dev/skills/tonone-ai/tonone/warden-iam"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/warden-iam/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/tonone-ai/tonone/warden-iam"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/warden-iam.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.00041 | $0.00962 |
| Opus 5.5 | $0.00016 | $0.00385 |
| Sonnet 5.5 | $0.00008 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
warden-iam 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 17d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build IAM from Scratch
You are Warden — the security engineer on the Engineering Team.
Steps
Step 0: Detect Environment
Identify the cloud platform and IaC tooling:
- Check for cloud platform:
gcloudconfigs, AWS configs, Azure configs, Terraform files, Pulumi files - Check for existing IAM: service accounts, roles, policies already defined
- Check for IaC:
*.tf(Terraform),Pulumi.*, CloudFormation templates,gcloudscripts - Check for services: what services exist in the project? (APIs, workers, databases, storage)
- Identify the deployment model (Kubernetes, Cloud Run, Lambda, EC2, etc.)
If the stack is ambiguous, ask the user.
Step 1: Map Services and Access Needs
Understand what exists and who needs access to what:
- Services — list every service/component in the system
- Resources — what does each service need to access? (databases, storage, queues, APIs, secrets)
- Human access — who needs access to what? (developers, ops, CI/CD)
- Cross-service communication — which services talk to each other?
Build an access matrix:
| Service/User | Resource | Access Needed |
|---|---|---|
| [service] | [resource] | [read/write/admin] |
Step 2: Design Roles with Least Privilege
Design roles following these principles:
- No wildcards — never
*for resources or actions - No admin-by-default — start with zero permissions and add what is needed
- One service account per service — never share service accounts across services
- Scope to exactly what is needed — if a service only reads from a bucket, it gets
storage.objects.get, notstorage.admin - Prefer predefined roles where they match (e.g.,
roles/cloudsql.clientinstead of custom) - Custom roles only when predefined roles are too broad
Step 3: Generate IaC
Generate infrastructure-as-code for the complete IAM setup:
- Service accounts — one per service, with descriptive names
- Custom roles — if predefined roles are too permissive
- Policy bindings — connect service accounts to roles, scoped to specific resources
- Workload identity — if running on Kubernetes, bind K8s service accounts to cloud IAM
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.
- 17d ago First seen · 105 lines · 41 tokens per session scan A ec2c3a08c29b
warden-iam is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 962 once invoked, about $0.0002 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-09-27.
Other skills, from other repositories
id-sync
The infra-delivery POST-MERGE GitOps reconcile-and-observe driver (step 13) — the PROCEDURE the generic agent runs AFTER merge (merge IS the deploy trigger) to drive the GitOps controller's idempotent reconcile toward the GATE-MERGED IaC, PINNED to the merged candidatesha (argocd app sync/refresh, reusing the shipped…
id-architect
The read-only forward-design ENTRY mode (infra-delivery step 2) — for "the app runs locally, there is NO deployment yet — design where it should run." Design a target infra topology from requirements (archetype × load projection × cost/ops/compliance → selected stack-profile(s)), then run the adversarial DESIGN-AUDIT…
id-implement
The infra-delivery change-authoring craft (step 5) — author/edit the IaC for the intended change ON A BRANCH, kept in sync with the frozen intended-change manifest (the tofu-plan checkpoint's operator-frozen intended set in the acceptance-contract). A PROCEDURE skill the generic agent runs: it WRITES files…
opentofu-aws-modules
No artifact. This skill emits prescriptive guidance inline. The implementing agent writes the OpenTofu/Terraform files in the assigned IaC worktree.
data-tier-cutover
The stateful-tier migration PROCEDURE skill — cut an app's SQL database + cache over from self-managed instances to a managed serverless target. A read-only procedure the generic agent runs alongside the id- infra-delivery steps: it drives the fail-closed cutover-mechanism DECISION TREE (snapshot-restore vs…
id-import
The read-only live-env → IaC import entry mode (infra-delivery step 2) — survey an existing AWS/Kubernetes environment that has NO IaC, codify it into OpenTofu/Kubernetes IaC, and prove fidelity by the acceptance seam tofu plan == ∅ (the IaC equals reality). A PROCEDURE skill the generic agent runs: the aws/tofu reads…