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/nirecom/agents/aws-scan-resourcesnpx skills add nirecom/agents --skill aws-scan-resourcesgit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/aws-scan-resources)<a href="https://agentmods.dev/skills/nirecom/agents/aws-scan-resources"><img src="https://agentmods.dev/badge/skills/nirecom/agents/aws-scan-resources.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.00028 | $0.00519 |
| Opus 5 | $0.00014 | $0.00260 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
aws-scan-resources 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
Procedure
ASR-1. Verify: aws CLI, AWS_PROFILE, AWS_STATE_DIR.
ASR-2. Enumerate with read-only CLI (pass --profile $AWS_PROFILE --region $AWS_DEFAULT_REGION on every call):
- EC2:
aws ec2 describe-instances --query 'Reservations[].Instances[].{id:InstanceId,state:State.Name,type:InstanceType}' - ECS:
aws ecs list-clusters+aws ecs list-services --cluster <name> - Lambda:
aws lambda list-functions --query 'Functions[].{name:FunctionName,runtime:Runtime}' - S3:
aws s3api list-buckets --query 'Buckets[].Name' - EBS:
aws ec2 describe-volumes --query 'Volumes[].{id:VolumeId,size:Size,state:State}' - RDS:
aws rds describe-db-instances --query 'DBInstances[].{id:DBInstanceIdentifier,engine:Engine}' - VPC/SG:
aws ec2 describe-vpcs,aws ec2 describe-security-groups - IAM:
aws iam list-users,aws iam list-roles,aws iam list-policies --scope LocalASR-3. Write raw data to$AWS_STATE_DIR/resources-<YYYYMMDD>.json. Single-region scope. ASR-4. Write human-readable summary to$AWS_STATE_DIR/resources-<YYYYMMDD>.md: - Header: profile, region, scan timestamp
- Table: resource type | count | notes (e.g. running/stopped for EC2)
- No ARNs, IDs, or IP addresses. ASR-5. Print to conversation: resource type → count only (no ARNs, IDs, IPs).
Rules
- Read-only: list-, describe-, get-* only.
- Identifiers must NOT appear in conversation.
- Use --no-paginate; fall back to --max-items 1000 where needed.
- Skip on AccessDeniedException — log to state file, continue.
Skip Conditions
Skip if $AWS_STATE_DIR/resources-<YYYYMMDD>.json exists and is less than 4 hours old.
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 · 38 lines · 28 tokens per session scan A 31eaecc2b1da
aws-scan-resources is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 519 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…