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/culiops/culiops-agent/cost-optimize-plannpx skills add culiops/culiops-agent --skill cost-optimize-plangit clone --depth 1 https://github.com/culiops/culiops-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/culiops/culiops-agent/cost-optimize-plan)<a href="https://agentmods.dev/skills/culiops/culiops-agent/cost-optimize-plan"><img src="https://agentmods.dev/badge/skills/culiops/culiops-agent/cost-optimize-plan.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.00145 | $0.09162 |
| Opus 5 | $0.00072 | $0.04581 |
| Sonnet 5 | $0.00029 | $0.01832 |
| Haiku 4.5 | $0.00015 | $0.00916 |
Grade A, and why
cost-optimize-plan 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 5d 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Optimize Plan
Given a cloud-cost-investigate report, run a read-only per-action verification pass, triage each remediation across four dimensions (reversibility, blast radius, evidence of no-use, dependency footprint), and produce a tiered execution plan. Strict read-only Iron Law; per-batch operator approval for verification queries; no handoff to execution — operator drives iac-change-execution manually with the plan.
The Iron Law
NO MUTATIONS. EVER.
NO VERIFICATION QUERIES WITHOUT OPERATOR APPROVAL.
NO TIER ASSIGNMENT WITHOUT EVIDENCE.
NO HANDOFF TO EXECUTION — OPERATOR DRIVES.
- Law 1: Read-only. Cost APIs, resource-state APIs, metrics APIs, access-log queries only. No
delete/terminate/update/tag— not even "harmless" ones. - Law 2: Per-batch verification approval. All verification queries for the report are planned together, itemized with IAM perms + per-query API cost, and approved as one batch before any run.
- Law 3: Every tier assignment carries evidence. No item lands in 🟢 or 🚫 without a labelled signal — the verification result row points at the specific query and its output. Same discipline as
cloud-cost-investigate's source-labelled savings. - Law 4: Skill stops at the plan. Even when an item is 🟢 Fast win and the operator says "just run it" — the skill refuses. Operator opens
iac-change-executionseparately. Avoids skipping the per-changepre-flightgate.
Constraints (Non-Negotiable)
- Read-only. No mutations of any kind.
- Per-batch query approval. All verification queries pass GATE 2 as a single batch with IAM + cost itemization. No silent extensions.
- No playbook → manual review. Items whose
(cloud, action-type, resource-type)has noexamples/<cloud>/<action>.mdplaybook are markedmanual-review-requiredand parked in a dedicated section of the plan. Skill never invents a verification strategy on the fly. - Evidence required for every tier. No 🟢 / 🚫 without a verification signal. If a query failed, the item stays in 🔴 with
verification-incompleteevidence — never silently promoted. - Single report per run. Skill runs against one
cloud-cost-investigatereport at a time. Combining reports across accounts / time ranges is out of scope. - Catalog re-use, not re-fetch. Service-discovery catalog is consulted (if present) for dependency lookup — never re-discovered.
- Output:
.culiops/cost-optimize-plan/<scope-slug>-<YYYYMMDD-HHmm>.md. Scope-slug matches the upstream report's slug, so plan files line up next to the investigation they triage. - Stop on query failure. Auth errors, rate limits, throttling halt the run and surface to operator. The skill does not silently skip and produce a partial plan disguised as complete.
- No re-evaluation of savings. Upstream report's savings/source/confidence are copied verbatim into the plan. This skill adds safety/triage columns alongside.
- No handoff automation. Plan ends at GATE 3 commit. Even a single fast-win item does not trigger
iac-change-executionautomatically.
What ships with it
16 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.
- examples/aws.md 2.6 KB
- examples/aws/delete-idle-ec2.md 2.5 KB
- examples/aws/delete-idle-elastic-ip.md 2.1 KB
- examples/aws/delete-kinesis-stream.md 8.2 KB
- examples/aws/delete-lambda.md 5.2 KB
- examples/aws/delete-nat-gateway.md 3.8 KB
- examples/aws/delete-orphaned-snapshot.md 1.7 KB
- examples/aws/delete-s3-bucket.md 3.2 KB
- examples/aws/delete-unattached-ebs.md 1.8 KB
- examples/aws/delete-unused-load-balancer.md 3.2 KB
- examples/aws/lifecycle-s3.md 2.3 KB
- examples/aws/rightsize-dynamodb.md 6.6 KB
- examples/aws/rightsize-ec2.md 3.1 KB
- examples/aws/rightsize-eks-nodegroup.md 6.9 KB
- examples/aws/rightsize-kinesis-stream.md 10 KB
- examples/aws/rightsize-rds.md 2.8 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.
- 5d ago First seen · 499 lines · 145 tokens per session scan A 345666a2c530
cost-optimize-plan is a skill published in the GitHub repository culiops/culiops-agent (2 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 9,162 once invoked, about $0.0007 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
aws-cost-operations
AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture. Essential when user mentions AWS costs, spending, billing,...
aws-cost-cleanup
Automated cleanup of unused AWS resources to reduce costs.
azure-compute
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost…
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
cost-optimization
Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost…
database-cloud-optimization-cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.