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/borhen68/skillengine/cost-optimizationnpx skills add borhen68/SkillEngine --skill cost-optimizationgit clone --depth 1 https://github.com/borhen68/SkillEngineWhat 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.00052 | $0.02423 |
| Opus 5 | $0.00026 | $0.01211 |
| Sonnet 5 | $0.00010 | $0.00485 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
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 2d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Optimization
Overview
Cost optimization is not about being cheap — it's about spending money where it creates value and eliminating waste. In cloud environments, costs compound silently: oversized instances, forgotten dev environments, unoptimized storage tiers, and data transfer charges that nobody tracks. This skill provides a systematic approach to finding and eliminating waste while maintaining (or improving) system reliability.
The 80/20 rule of cloud costs: 80% of your bill comes from 20% of your resources. Focus on the big items first.
When to Use
- Monthly cloud bill has grown > 20% without corresponding traffic growth
- Setting up new infrastructure and want cost-aware defaults
- Reviewing architecture for a system that's been running > 6 months
- Preparing for scaling events (launch, Black Friday, viral growth)
- Evaluating multi-cloud vs single-cloud strategies
- After an audit reveals "surprise" charges (data transfer, API calls, storage)
NOT for:
- Systems where reliability is worth any cost (life-critical, financial trading)
- One-time cost reduction without ongoing monitoring (costs creep back)
The Cost Optimization Process
Step 1: Measure and Allocate
You can't optimize what you can't measure. Before changing anything:
COST ALLOCATION FRAMEWORK:
├── Tag everything (owner, environment, product, cost-center)
├── Enable detailed billing exports (hourly granularity)
├── Set up cost anomaly detection
├── Allocate shared costs (network, monitoring, platform)
└── Create per-team visibility dashboards
Key metrics to track:
| Metric | Why It Matters | Target |
|---|---|---|
| Cost per request | Efficiency of serving traffic | Trending down |
| Cost per user | Unit economics | Trending down |
| Idle resource % | Waste identification | < 10% |
| Storage $/GB | Tier optimization | Match workload pattern |
| Data transfer | Often the "surprise" line item | < 10% of total |
Step 2: Identify Waste
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.
- 2d ago First seen · 301 lines · 52 tokens per session scan A 086d3b1087d3
cost-optimization is a skill published in the GitHub repository borhen68/SkillEngine (17 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 2,423 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
code-review-and-quality
执行多维度代码审查。用于合并任何变更之前；用于审查自己、其他 agent 或人类编写的代码；用于在代码进入主分支前从多个维度评估代码质量。.
code-simplification
为清晰度简化代码。用于在不改变行为的前提下重构代码以提升清晰度；用于代码能运行但比应有状态更难阅读、维护或扩展时；用于审查已累积不必要复杂度的代码时。.
doubt-driven-development
在每个非平凡决策成立前，用全新上下文进行对抗式审查。当正确性比速度更重要、处理不熟悉代码、风险较高（生产、安全敏感逻辑、不可逆操作），或任何自信输出现在验证比之后调试更便宜时使用。.
test-driven-development
用测试驱动开发。用于实现任何逻辑、修复任何 bug，或改变任何行为。用于需要证明代码能工作、收到 bug 报告，或即将修改现有功能时。.
api-and-interface-design
指导稳定的 API 和接口设计。设计 API、模块边界或任何公共接口时使用。创建 REST 或 GraphQL endpoint、定义模块之间的类型契约，或建立前后端边界时使用。.
ci-cd-and-automation
自动化 CI/CD pipeline 设置。用于设置或修改构建和部署 pipeline 时；用于需要自动化质量门禁、在 CI 中配置 test runners，或建立部署策略时。.