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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-cost)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-cost"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-cost/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/commands/christopherlouet/claude-base/ops-cost"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-cost.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.00000 | $0.00469 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
ops-cost 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 6d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS-COST Agent
Track and optimize costs: Claude Code token consumption and cloud infrastructure (FinOps).
Context
$ARGUMENTS
Objective
Two complementary cost angles:
- Claude Code tokens — analyze and display token consumption metrics to reduce usage cost.
- Cloud infrastructure (FinOps) — identify opportunities to cut cloud spend without impacting performance or availability, with an actionable report.
Measurement tools
ccusage (recommended)
# Installation
pip install ccusage
# Total consumption
ccusage
# Per project
ccusage --project
# Per day
ccusage --daily
# Specific period
ccusage --since 2026-03-01 --until 2026-03-23
Reduction strategies
| Strategy | Savings | How |
|---|---|---|
/compact between phases |
20-40% | Reduce accumulated context |
| Haiku agents for simple tasks | 50-70% | Exploration, reading, search |
| Focused session scope | 30-50% | 1-5 tasks per session max |
| Lightweight CLAUDE.md files | 10-20% | Less context loaded at startup |
Cloud infrastructure cost optimization (FinOps)
For the cloud-spend angle:
- Establish cost visibility (tags, per-provider tools).
- Right-size (CPU, memory, disk, network); schedule auto-stop for non-prod environments.
- Analyze commitments (Reserved, Savings Plans, Spot); spot orphan resources, CDN, ARM.
- Produce a report: current spend, identified savings, required effort — split into quick wins (< 1 week), medium- and long-term actions; define FinOps metrics to track.
- IMPORTANT: never optimize at the expense of availability or security; set budget alerts BEFORE optimizing; never delete resources without verifying actual usage.
Expected output
- Token metrics: tokens consumed (input/output), estimated cost, trends per day/week
- Cloud FinOps report: current spend, savings, quick wins + medium/long-term actions
- Recommendations: applicable optimization strategies (both angles)
IMPORTANT: ccusage reads Claude Code local logs, no data is sent externally.
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.
- 6d ago First seen · 66 lines · 0 tokens per session scan A fe3bd654b79d
ops-cost is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 tokens. 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 commands, from other repositories
context-stats
Display context window usage and token statistics.
migrate
Generate and manage database migrations.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
log-decision
Append an architectural decision to the persistent decision log.
update-docs
Scan for recently modified files and update corresponding documentation.
backup-config
Backup Claude Code configuration files.