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 aws/tools-for-devops-agent --skill guardduty-cost-optimizationgit clone --depth 1 https://github.com/aws/tools-for-devops-agentWrote 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/aws/tools-for-devops-agent/guardduty-cost-optimization)<a href="https://agentmods.dev/skills/aws/tools-for-devops-agent/guardduty-cost-optimization"><img src="https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/guardduty-cost-optimization/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/aws/tools-for-devops-agent/guardduty-cost-optimization"><img src="https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/guardduty-cost-optimization.svg" alt="Reviewed on agentmods" width="80" 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.00185 | $0.02335 |
| Opus 5.5 | $0.00074 | $0.00934 |
| Sonnet 5.5 | $0.00037 | $0.00467 |
| Haiku 4.5 | $0.00018 | $0.00233 |
Grade A, and why
guardduty-cost-optimization 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 8d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon GuardDuty Cost Optimization
Identify, quantify, and prioritize Amazon GuardDuty cost optimization opportunities aligned with Monitoring GuardDuty usage and estimating costs and GuardDuty pricing.
This skill uses read-only GuardDuty, CloudWatch, and Organizations APIs only. It never enables, disables, or reconfigures a detector or protection plan — all remediation is delivered as recommendations for a human to review and apply. It reads usage metrics and findings statistics only; it does not read finding detail content.
When to Use
Activate this skill when the user asks to:
- Reduce or optimize Amazon GuardDuty costs
- Investigate an unexpected GuardDuty cost increase
- Understand which protection plan or data source drives GuardDuty spend
- Decide whether a protection plan (S3 Protection, Runtime Monitoring, etc.) is worth its cost
- Project GuardDuty spend after the 30-day free trial
- Perform a GuardDuty cost review or FinOps assessment
How GuardDuty Billing Works
The pricing model is the foundation of every finding below. The essentials:
- GuardDuty is pay-as-you-go, per protection plan, priced on the volume of data each plan analyzes. There is no per-detector fee — cost is driven entirely by analyzed volume, and each plan meters on its own unit (counts, bytes, or vCPU/ACU hours).
- Runtime Monitoring offsets VPC Flow Log charges — for instances the Runtime Monitoring agent covers, GuardDuty stops charging for VPC Flow Log processing. The two line items trade against each other; size the net effect.
- Your own log configuration does not reduce GuardDuty cost — GuardDuty ingests from independent internal sources. The only cost lever is the GuardDuty protection-plan configuration itself.
For the full per-plan metric/unit/pricing table, the two critical billing behaviors, and byte-to-GB/TB conversions, load references/billing-model.md when identifying which plan drives a charge or reasoning about the Runtime Monitoring offset.
What ships with it
37 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.
- .skilleval.yaml 255 B
- assets/report-template.md 2.6 KB
- CHANGELOG.md 4.1 KB
- evals/best-practices/v1/benchmark.json 6.6 KB
- evals/best-practices/v1/iteration-1/best-practices-tests-results.json 9.4 KB
- evals/eval_queries.json 741 B
- evals/evals.json 5.7 KB
- evals/files/guardduty-context.json 780 B
- evals/functional/v1/benchmark.json 88 KB
- evals/functional/v1/evals.json 5.7 KB
- evals/functional/v1/iteration-1/guardduty-cost-log-config-quirk/with_skill/functional-tests-results.json 3.1 KB
- evals/functional/v1/iteration-1/guardduty-cost-log-config-quirk/with_skill/outputs/journal_records.json 18 KB
- evals/functional/v1/iteration-1/guardduty-cost-log-config-quirk/without_skill/functional-tests-results.json 3.4 KB
- evals/functional/v1/iteration-1/guardduty-cost-log-config-quirk/without_skill/outputs/journal_records.json 17 KB
- evals/functional/v1/iteration-1/guardduty-cost-negative-trigger/with_skill/functional-tests-results.json 446 B
- evals/functional/v1/iteration-1/guardduty-cost-negative-trigger/with_skill/outputs/journal_records.json 5.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-agent-gap/with_skill/functional-tests-results.json 5.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-agent-gap/with_skill/outputs/journal_records.json 9.8 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-agent-gap/without_skill/functional-tests-results.json 4.5 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-agent-gap/without_skill/outputs/journal_records.json 21 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-offset/with_skill/functional-tests-results.json 3.2 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-offset/with_skill/outputs/journal_records.json 17 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-offset/without_skill/functional-tests-results.json 4.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-runtime-offset/without_skill/outputs/journal_records.json 19 KB
- evals/functional/v1/iteration-1/guardduty-cost-security-tradeoff/with_skill/functional-tests-results.json 3.0 KB
- evals/functional/v1/iteration-1/guardduty-cost-security-tradeoff/with_skill/outputs/journal_records.json 19 KB
- evals/functional/v1/iteration-1/guardduty-cost-security-tradeoff/without_skill/functional-tests-results.json 1.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-security-tradeoff/without_skill/outputs/journal_records.json 2.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-severity-definitions/with_skill/functional-tests-results.json 2.6 KB
- evals/functional/v1/iteration-1/guardduty-cost-severity-definitions/with_skill/outputs/journal_records.json 16 KB
- evals/functional/v1/iteration-1/guardduty-cost-severity-definitions/without_skill/functional-tests-results.json 2.9 KB
- evals/functional/v1/iteration-1/guardduty-cost-severity-definitions/without_skill/outputs/journal_records.json 14 KB
- evals/structure/structure-tests-results-v1.json 3.4 KB
- README.md 6.0 KB
- references/billing-model.md 2.8 KB
- references/data-collection.md 2.1 KB
- references/opportunities.md 4.4 KB
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.
- 8d ago First seen · 174 lines · 185 tokens per session scan A c04acffeb4c5
guardduty-cost-optimization is a skill published in the GitHub repository aws/tools-for-devops-agent (107 stars, last pushed today), licensed Apache-2.0. It adds 185 tokens to every session and 2,335 once invoked, about $0.0007 per session on Opus 5.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-10-08.
Other skills, from other repositories
Cloud Billing Analyst
FOCUS-first analyst for cloud billing data across AWS, Azure, GCP, OCI, and SaaS. Translates raw exports into Finance, Engineering, and Leadership narratives. Knows provider-native quirks (CUR / Cost Management / BigQuery export) but defaults to FOCUS columns for portability.
Commitment Discount Strategist
Cross-cloud commitment portfolio specialist. Designs and maintains Reserved Instances, Savings Plans, Reservations, and Committed Use Discounts across AWS, Azure, GCP, and OCI using FOCUS Commitment Discount columns. Maximizes effective discount without bleeding on unused commitment.
Budget & Anomaly Operator
Designs and tunes the alerting layer for cloud spend -- both budget-trajectory alerts (Budgeting capability) and statistical anomaly detection (Anomaly Management capability). Optimizes for precision and time-to-action, not coverage.
AWS Cost Explorer Analyst
Expert analyst for AWS Cost Explorer, Cost and Usage Report (CUR), and Cost Categories. Turns raw billing line items into service-level, team-level, and workload-level narratives that drive action.
Cost Anomaly Detector
Builds and tunes anomaly detection for cloud spend -- z-score, seasonal decomposition, and segment-aware baselines that surface real issues without drowning teams in false positives.
Azure Cost Management Navigator
Expert in Azure Cost Management, enterprise enrollments, subscriptions, management groups, and the specific shape of Azure billing exports -- FOCUS, EA, MCA, and CSP scenarios.