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 harness/harness-ai --skill analyze-costsgit clone --depth 1 https://github.com/harness/harness-aiWrote 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/harness/harness-ai/analyze-costs)<a href="https://agentmods.dev/skills/harness/harness-ai/analyze-costs"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/analyze-costs/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/harness/harness-ai/analyze-costs"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/analyze-costs.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.00053 | $0.01156 |
| Opus 5 | $0.00026 | $0.00578 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
analyze-costs 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 10d 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.
This is a copy
100% identical to analyze-costs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Costs
Analyze cloud costs and identify savings using Harness Cloud Cost Management (CCM) via MCP.
Instructions
Step 1: Get Cost Overview
Call MCP tool: harness_get
Parameters:
resource_type: "cost_account_overview"
Returns total spend, provider breakdown, and trend vs previous period.
Step 2: Get Cost Breakdown
Call MCP tool: harness_get
Parameters:
resource_type: "cost_breakdown"
Multi-dimensional breakdown by service, environment, team, region.
Step 3: Explore Perspectives
Call MCP tool: harness_list
Parameters:
resource_type: "cost_perspective"
Then get detailed data for a specific perspective:
Call MCP tool: harness_get
Parameters:
resource_type: "cost_perspective"
resource_id: "<perspective_id>"
Step 4: Get Cost Trends
Call MCP tool: harness_get
Parameters:
resource_type: "cost_timeseries"
Step 5: Get Optimization Recommendations
Call MCP tool: harness_list
Parameters:
resource_type: "cost_recommendation"
For detailed recommendation info:
Call MCP tool: harness_get
Parameters:
resource_type: "cost_recommendation_detail"
resource_id: "<recommendation_id>"
Summary statistics:
Call MCP tool: harness_get
Parameters:
resource_type: "cost_recommendation_stats"
Step 6: Check for Anomalies
Call MCP tool: harness_list
Parameters:
resource_type: "cost_anomaly"
To dismiss a known anomaly:
Call MCP tool: harness_execute
Parameters:
resource_type: "cost_anomaly"
action: "report_feedback"
resource_id: "<anomaly_id>"
body: { feedback: "FALSE_ANOMALY" } # or TRUE_ANOMALY / NOT_RESPONDED
Step 7: Commitment Analysis
Call MCP tool: harness_get
Parameters:
resource_type: "cost_commitment"
Report Format
## Cloud Cost Analysis
**Period:** Last 30 Days
### Summary
| Provider | Spend | vs Previous |
|----------|-------|-------------|
| AWS | $X | +X% |
| GCP | $X | +X% |
| Azure | $X | -X% |
### Top Recommendations
1. **Rightsize <resource>** - Save $X/month (95% confidence)
2. **Convert to Reserved** - Save $X/month
3. **Delete unused resources** - Save $X/month
### Anomalies
- <date>: <service> spiked $X above expected
### Actions
- [ ] Rightsize instance X
- [ ] Purchase reserved capacity
- [ ] Clean up unused volumes
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.
- 10d ago First seen · 186 lines · 53 tokens per session scan A 67b082f57294
analyze-costs is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 19d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,156 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyze-costs, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…