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 agentmods add skills/soulcodex/agentic/use-aws-mini-stack-emulatornpx skills add soulcodex/agentic --skill use-aws-mini-stack-emulatorgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/use-aws-mini-stack-emulator)<a href="https://agentmods.dev/skills/soulcodex/agentic/use-aws-mini-stack-emulator"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/use-aws-mini-stack-emulator.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 | $0.00049 | $0.00495 |
| Opus 5 | $0.00024 | $0.00247 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
use-aws-mini-stack-emulator 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 3d 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
Use AWS Mini Stack Emulator Skill
Use local AWS emulation to accelerate Terraform feedback loops where appropriate.
Always pair this skill with terraform-risk-playbook. That skill is
authoritative for the response contract, failure-mode classification,
version/runtime guards, validation chain, and rollback notes.
Step 1 - Select Emulator Scope
Use emulator-compatibility-matrix.md to decide what is safe to validate locally.
Classify each planned check as:
- emulator-suitable
- partial confidence only
- requires real AWS
Step 2 - Configure Provider and Endpoints for Local Runs
Keep local endpoint wiring isolated from production configuration. Use explicit
variables or per-environment override files for emulator endpoint settings.
Use local state or terraform init -backend=false for emulator-first CI checks
to avoid touching shared remote backends.
Step 3 - Validate Fast Feedback Cases
Good emulator targets:
- syntax and interpolation mistakes
- module wiring and basic dependencies
- selected resource contract checks where behavior is reliably emulated
Step 4 - Document Gaps and Escalate
Always document unsupported services/behaviors and escalate those tests to real AWS validation before merge.
Step 5 - Keep Scope Boundary Explicit
This skill is for local acceleration only. It does not replace real AWS plan/apply verification for production-impacting infrastructure.
It cannot prove:
- production backend locking or state migration behavior
- IAM or service semantics that emulators do not model faithfully
- reviewed plan artifact and approval parity in CI
- final confidence for production-impacting provider/runtime upgrades
Avoid overlap with docker-compose-local-setup: this skill covers Terraform + AWS
emulation behavior, not generic multi-service compose orchestration design.
What ships with it
1 file 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.
- 3d ago First seen · 72 lines · 49 tokens per session scan A 4164651dd4fd
use-aws-mini-stack-emulator is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 495 once invoked, about $0.0002 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
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
design-system-governance
Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use design-system-adoption (designer-toolkit); for design file history use version-control-strategy (design-ops).
motion-system
Define motion tokens — durations, easing vocabulary, and reduced-motion handling — for consistency product-wide. Use when standardising motion across a system. For crafting one specific animation, use animation-principles (interaction-design).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
design-token-audit
Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use design-token (design-systems).
design-token
Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use design-token-audit (designer-toolkit); for multi-brand mapping use theming-system.