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/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/aws)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/aws"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/aws.svg" alt="Measured on agentmods" 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.00070 | $0.03917 |
| Opus 5 | $0.00035 | $0.01959 |
| Sonnet 5 | $0.00014 | $0.00783 |
| Haiku 4.5 | $0.00007 | $0.00392 |
Grade A, and why
aws 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 7d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Command
Structured guidance for AWS CloudFront, WAF, Lambda@Edge, and multi-account security patterns.
Interactive Wizard (fires when no mode is provided)
When invoked with no arguments, ask before proceeding:
Q1 — Mode?
What do you need?
1. cloudfront — distributions, OAC, cache policies, security headers, Lambda@Edge
2. waf — web ACLs, managed rule groups, rate limiting, false positive tuning
3. lambda-edge — CloudFront Functions vs Lambda@Edge, viewer/origin events
4. multi-account — Firewall Manager, cross-account OAC, FMS WAF enforcement
5. orgs — Organizations, SCPs, OU design, account vending, Control Tower
6. review — production-readiness review of CloudFront + WAF config
7. terraform — generate a Terraform module scaffold
Enter 1–7 or mode name:
Q2 — Context (after mode selected):
- cloudfront:
Describe the issue or what you want to build (distribution, OAC, cache, edge function): - waf:
Describe the use case — new WebACL, false positive, adding a rule, or multi-account enforcement: - lambda-edge:
What does the edge function need to do? (auth, URL rewrite, A/B test, dynamic routing): - multi-account:
How many accounts? Do you have FMS administrator configured in the security account? - orgs:
Describe what you need — SCP enforcement, OU design, account vending, or Control Tower setup: - review / terraform: no follow-up needed — proceed directly
Activation
Invoke with /platform-skills:aws followed by a mode, or describe your problem and the command will route automatically.
/platform-skills:aws cloudfront # CloudFront distributions, OAC, cache, security headers
/platform-skills:aws waf # WAF web ACLs, managed rules, rate limiting
/platform-skills:aws lambda-edge # Lambda@Edge and CloudFront Functions
/platform-skills:aws multi-account # Firewall Manager, cross-account, Organizations
/platform-skills:aws review # Production-readiness review of your config
/platform-skills:aws terraform # Generate Terraform module scaffold
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.
- 7d ago First seen · 414 lines · 70 tokens per session scan A 87be6f5ccd56
aws is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 70 tokens to every session and 3,917 once invoked, about $0.0003 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-30.
Other commands, from other repositories
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
conjure-config
Set, view, or remove conjure preferences. Asks questions to understand what you want, then writes plain-language instructions that conjure commands follow automatically.
conjure-agent
Creates or updates a Claude Code agent definition (/.claude/agents/ .md or project-local).
conjure
Use when you want to build a new Claude Code skill, agent, hook, or MCP server but aren't sure which — or when you want to describe what you want in plain language. Auto-detects the right artifact type, asks targeted questions, explains the reasoning, then builds it.
conjure-mcp
Create a Claude Code MCP (Model Context Protocol) server. Provide a description of what external system or data source you want Claude to connect to.
conjure-help
Show help for the conjure toolkit — all commands, argument syntax, update modes, and decision guide. Use when you want to know which conjure command to use or how any conjure command works.