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 jnPiyush/AgentX --skill cost-analysisgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/cost-analysis)<a href="https://agentmods.dev/skills/jnpiyush/agentx/cost-analysis"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/cost-analysis/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/jnpiyush/agentx/cost-analysis"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/cost-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.01393 |
| Opus 5.5 | $0.00027 | $0.00557 |
| Sonnet 5.5 | $0.00014 | $0.00279 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
cost-analysis 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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Analysis
Purpose: Make running cost a first-class, comparable dimension of an architecture decision -- not a surprise discovered after deployment.
When to Use This Skill
- Writing an ADR: every option in the comparison table needs a cost column
- Sizing a prototype that will sit idle most of its life
- Choosing between managed, serverless, and always-on compute
- A stakeholder asks "what does it cost to leave this running for a month?"
Do NOT use for billing forensics on already-deployed resources -- that is an observability task, not an architecture task.
Core Model: Idle Cost Is The Prototype Killer
A prototype is active for a small slice of the month and idle for the rest. Total cost is therefore driven far more by the idle floor than by peak throughput.
monthly_cost = (active_hours * active_rate) + (idle_hours * idle_rate) + fixed_monthly
| Billing shape | idle_rate |
Prototype impact |
|---|---|---|
| Consumption / serverless | ~0 | Cheap when idle -- prefer for prototypes |
| Auto-pause (serverless DB) | storage floor only | Cheap, small floor remains |
| Provisioned / always-on | full rate | Dominates the bill -- flag it |
| Fixed monthly (gateway, IP) | n/a | Unavoidable floor -- surface it explicitly |
Rule: If a component's
idle_rateequals itsactive_rate, the estimate MUST call it out as an always-on floor. That single line changes most prototype decisions.
Load Envelopes
Estimate against three declared envelopes, never a single number. Each envelope is a set of stated assumptions, so a reviewer can challenge the input rather than the total.
| Envelope | Intent | Typical assumptions |
|---|---|---|
pilot |
Demo / stakeholder review | Few users, hours per day, bursty |
team |
Real internal usage | Business hours, steady load |
org |
Scale sanity check | Continuous load, growth headroom |
Envelope assumptions live in the cost model file, not in prose, so they are diffable.
What ships with it
3 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.
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.
- 1mo ago Changed 30c7811c031d
- 1mo ago First seen · 151 lines · 68 tokens per session scan A 35d44010f1ed
cost-analysis is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,393 once invoked, about $0.0003 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-09-03.
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-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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
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…
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".