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/event4u-app/agent-config/aws-infrastructurenpx skills add event4u-app/agent-config --skill aws-infrastructuregit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/aws-infrastructure)<a href="https://agentmods.dev/skills/event4u-app/agent-config/aws-infrastructure"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/aws-infrastructure.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.00047 | $0.01747 |
| Opus 5 | $0.00023 | $0.00873 |
| Sonnet 5 | $0.00009 | $0.00349 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
aws-infrastructure 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 yesterday.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aws-infrastructure
When to use
Use this skill when working with AWS infrastructure, deployment configurations, ECS task definitions, or environment-specific settings.
Do NOT use when:
- Local development setup (use
dockerskill) - Application code changes
Procedure: Modify AWS infrastructure
- Read the
.aws/directory (or equivalent) for environment configs and templates. - Read CI/CD workflows (e.g.,
.github/workflows/) for the deployment pipeline. - Check the environment-specific vars files.
- Read project-level overrides — check
agents/overrides/skills/aws-infrastructure.mdfor project-specific service names, prefixes, and infrastructure details.
Architecture overview
Environments (typical setup)
| Environment | Trigger | Notes |
|---|---|---|
| Review | PR with label | Ephemeral, per-branch |
| Stage | Push to main |
Persistent, pre-production |
| Production | Release tag | Persistent, live |
Common AWS services
| Service | Purpose |
|---|---|
| ECS Fargate | Container orchestration (no EC2 instances) |
| ECR | Docker image registry |
| EFS | Shared filesystem (private + public access points) |
| Secrets Manager | .env file storage per environment |
| IAM Roles | OIDC-based GitHub Actions authentication |
| VPC | Networking (security groups, subnets) |
Vars file structure
Environment-specific config files (e.g., .aws/*.vars.yaml) typically contain:
AWS:
GlobalPrefix: {project}-{env} # Resource naming prefix
Region: eu-central-1 # AWS region
RoleArn: arn:aws:iam::... # GitHub Actions OIDC role
ECS:
Cluster: {project}-{env} # ECS cluster name
VPC:
SecurityGroups: [...]
Subnets: [...]
EFS:
FileSystemId: fs-...
Read the actual vars files in the project for concrete values.
Template structure
Templates commonly use gomplate for rendering. Typical templates:
| Template | Purpose |
|---|---|
task-definition-web.tpl.yaml |
Web server (app + reverse proxy) |
task-definition-worker.tpl.yaml |
Queue worker |
task-definition-scheduler.tpl.yaml |
Task scheduler (cron) |
task-definition-migrations.tpl.yaml |
One-shot migration runner |
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.
- yesterday Changed · +41 lines 0472914f145b
- 6d ago First seen · 158 lines · 47 tokens per session scan A 358d41c5c5e0
aws-infrastructure is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,747 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
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
diag-k8s-pod-crashloop
K8s Pod CrashLoopBackOff 全链排查。从 kubectl describe → events → logs → restart policy → resource limits → liveness/readiness probe → image pull → configmap/secret 挂载，定位根因并输出修复建议。.
Apache Airflow MCP
Skill "Apache Airflow MCP" from agentskillexchange/skills, covering apache airflow mcp, prerequisites, installation, documentation and source.
k8s-manifests
When writing K8s YAML, designing Helm charts, setting resource limits, configuring probes, or reviewing pod security.
cloud-run
Deploy headless robotics / sim / demo containers to Google Cloud Run: the build → Artifact Registry → Cloud Run path plus the gotchas that bite sim workloads (no UDP multicast for gz-transport/DDS, CPU allocated only while a request is open, session affinity for per-visitor instances, request timeout / concurrency for…