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 commands/lazorgurl/terror/costsgit clone --depth 1 https://github.com/lazorgurl/terrorWhat 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.00013 | $0.00325 |
| Opus 5 | $0.00006 | $0.00162 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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 yesterday.
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.
What it actually says
Infrastructure Costs
Analyze and present infrastructure cost information.
Steps
-
Current spend. Call
terror_statusand provider-specific tools to gather resource inventory. For each resource, estimate monthly cost based on type and configuration:- Compute: instance type, hours running
- Storage: capacity, access tier, egress
- Database: instance tier, storage, backups
- Networking: load balancers, NAT gateways, egress
-
Cost breakdown. Present costs grouped by:
- Provider
- Resource type
- Environment (production vs staging vs dev)
- Team or project (based on labels/tags)
-
Optimization opportunities. Identify savings:
- Idle or underutilized resources (low CPU, no traffic)
- Resources that could use committed use discounts or reserved instances
- Oversized instances relative to actual usage
- Dev/staging resources running 24/7 that could be scheduled
- Unattached disks, unused IPs, orphaned snapshots
-
Planned changes. If the user has pending Terror plans, estimate the cost delta:
- What the new resources will cost
- What resources are being removed
- Net monthly impact
-
Present summary. Show:
- Total estimated monthly cost
- Top 5 most expensive resources
- Top 3 optimization opportunities with estimated savings
- Cost trend if historical data is available
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.
- yesterday First seen · 41 lines · 13 tokens per session scan A ddd087eb327d
costs is a command published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 325 once invoked, about $0.0001 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 commands, from other repositories
account
This API allows you to manage your Scaleway Projects.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy
Build, test, deploy with staged rollout.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.