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 skills add automateyournetwork/netclaw --skill aws-cloud-monitoringgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/aws-cloud-monitoring)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/aws-cloud-monitoring"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/aws-cloud-monitoring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/aws-cloud-monitoring"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/aws-cloud-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 13 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.00050 | $0.00916 |
| Opus 5 | $0.00025 | $0.00458 |
| Sonnet 5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
aws-cloud-monitoring 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 13d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Cloud Monitoring
MCP Server
- Command:
uvx awslabs.cloudwatch-mcp-server@latest(stdio transport) - Requires:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_REGION(orAWS_PROFILE)
Key Capabilities
- Metrics: Query CloudWatch metrics for any AWS service (EC2, ELB, TGW, NAT GW, VPN)
- Alarms: List and inspect CloudWatch alarms and their states
- Logs: Run CloudWatch Logs Insights queries across any log group
- Flow Logs: Analyze VPC and TGW flow logs for traffic patterns and dropped connections
Workflow: Network Monitoring Dashboard
When a user asks "how is our AWS network performing?":
- Check alarms: List CloudWatch alarms in ALARM state
- VPN metrics: Tunnel state, bytes in/out for site-to-site VPNs
- NAT Gateway metrics: Active connections, packets dropped, bytes processed
- Transit Gateway metrics: Bytes in/out, packets dropped per attachment
- ELB metrics: Healthy/unhealthy targets, latency, 5xx errors
- Report: Network health dashboard with any issues flagged
Workflow: Flow Log Analysis
When investigating traffic patterns or security events:
- Query VPC flow logs: Filter by source IP, destination IP, port, action (ACCEPT/REJECT)
- Identify rejected traffic: Find REJECT entries to see blocked connections
- Top talkers: Aggregate by source/destination to find heaviest traffic flows
- Time correlation: Narrow to specific time windows around incidents
- Report: Traffic analysis with recommendations
Common CloudWatch Network Metrics
| Service | Metric | What It Tells You |
|---|---|---|
| VPN | TunnelState |
0=down, 1=up for each tunnel |
| VPN | TunnelDataIn/Out |
Bytes through each VPN tunnel |
| NAT GW | ActiveConnectionCount |
Active NAT connections |
| NAT GW | PacketsDropCount |
Packets dropped (capacity issue) |
| NAT GW | BytesProcessed |
Traffic volume through NAT |
| TGW | BytesIn/BytesOut |
Traffic per TGW attachment |
| TGW | PacketDropCountBlackhole |
Blackhole route drops |
| ELB | HealthyHostCount |
Healthy targets behind ALB/NLB |
| ELB | TargetResponseTime |
Backend latency |
| EC2 | NetworkIn/NetworkOut |
Instance network throughput |
| EC2 | NetworkPacketsIn/Out |
Instance packet rate |
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.
- 13d ago First seen · 91 lines · 50 tokens per session scan A 156305d4e733
aws-cloud-monitoring is a skill published in the GitHub repository automateyournetwork/netclaw (657 stars, last pushed 6d ago), licensed Apache-2.0. It adds 50 tokens to every session and 916 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 skills, from other repositories
cis-aws-foundations-5.12
Ensure changes to network gateways are monitored.
cis-aws-foundations-5.13
Ensure route table changes are monitored.
cis-aws-foundations-5.15
Ensure AWS Organizations changes are monitored.
cis-aws-foundations-5.3
Ensure usage of the 'root' account is monitored.
cis-aws-foundations-5.7
Ensure disabling or scheduled deletion of customer created CMKs is monitored.
cis-aws-foundations-5.8
Ensure S3 bucket policy changes are monitored.