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/awslabs/agent-plugins/aws-lambda-microvmsnpx skills add awslabs/agent-plugins --skill aws-lambda-microvmsgit clone --depth 1 https://github.com/awslabs/agent-pluginsWhat 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.00164 | $0.03605 |
| Opus 5 | $0.00082 | $0.01802 |
| Sonnet 5 | $0.00033 | $0.00721 |
| Haiku 4.5 | $0.00016 | $0.00361 |
Grade A, and why
aws-lambda-microvms scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "<endpoint>/" -H "X-aws-proxy-auth: $TOKEN" How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Lambda MicroVMs
The AWS MCP server is recommended for sandboxed execution and audit logging.
AWS Lambda MicroVMs are serverless compute environments that combine Firecracker VM isolation with container-like efficiency. Each MicroVM:
- Runs your application as a container inside a Firecracker microVM — you can reproduce the environment locally.
- Runs Amazon Linux 2023 as the base OS inside the MicroVM.
- Boots from a memory + disk snapshot captured at image build time, so application init is skipped on run.
- Has a dedicated, TLS-terminated HTTPS endpoint reachable with an auth token.
- Can be suspended and resumed with state preserved; lives up to 8 hours.
Two-resource model:
MicrovmImage— a versioned artifact built from{S3 zip with Dockerfile} + baseImageArn. Each version has per-architecture/chipsetBuilds.Microvm— a running instance created (RunMicrovm) from an image version.
Two roles:
buildRoleArn— used during image build (S3 read, CloudWatch logs, optional ECR).executionRoleArn— assumed at runtime by the running MicroVM.
When to use
Choose Lambda MicroVMs when
- Analytics workloads — isolated compute for data processing, ETL jobs, or query execution with strong tenant separation.
- AI / agent code execution sandboxes — fresh, isolated environment per session, fast resume between turns.
- Interactive code playgrounds & notebooks — Jupyter, REPLs, dev environments executing user code.
- Reinforcement-learning environments — clean per-episode envs with tool access.
- Multi-tenant CI executors / build runners — strong tenant isolation.
- Game / simulation servers — sessionful, long-lived (up to 8 hr) workloads.
- Security scanning — running untrusted analyzers in isolation.
In general, Lambda MicroVMs are suited for long-lived sessions, real port-listening servers (gRPC, WebSocket, custom TCP protocols), state preserved across periods of inactivity (suspend/resume), container-level access (FUSE, eBPF, custom syscalls), or session-affine routing to a specific compute environment.
What ships with it
6 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.
- yesterday First seen · 226 lines · 164 tokens per session scan A 8b90386e379e
aws-lambda-microvms is a skill published in the GitHub repository awslabs/agent-plugins (876 stars, last pushed 5d ago), licensed Apache-2.0. It adds 164 tokens to every session and 3,605 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
redshift-support-specialist
Amazon Redshift domain expertise for query optimization, operational reviews, and cost optimization on provisioned clusters and Serverless workgroups. Use when a user asks about Redshift query tuning, slow queries, disk spill, distribution/sort key issues, a Redshift health check or operational review, or Redshift…
database-rds-devops
Database-level data-plane diagnostics for Aurora MySQL and Aurora PostgreSQL. Executes predefined read-only health check queries via RDS Data API to analyze buffer pool, connections, locks, replication, storage, performance, and index efficiency. Requires the rds-aidba MCP server for database-internal access beyond…
eks-operation-review
Comprehensive Amazon EKS operational review aligned with the AWS EKS Best Practices Guide. Use this skill when a user asks to review, audit, or assess EKS clusters for best practices compliance, operational readiness, security posture, cost optimization, reliability, networking, scalability, or upgrade readiness.…
investigation-cost-guardrail
Cost guardrail for AWS DevOps Agent that covers ALL AWS services and native agent tools. Before the agent makes any paid API call, this skill estimates cost, enforces budgets per investigation, detects expensive operations across all services (Athena queries, S3 scans, DynamoDB scans, SageMaker inference, PromQL…
cis-aws-foundations-3.2.3
Ensure that RDS instances are not publicly accessible.
bedrock-adoption-readiness
Amazon Bedrock production readiness assessment covering IAM governance, data retention (ZDR), quota and capacity headroom, and operational observability across Standard Bedrock and Mantle surfaces. Use this skill when a user asks to review Bedrock readiness, assess Bedrock security posture, evaluate quota headroom…