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/benkapner/claude-code-basecamp/cost-speed-meternpx skills add Benkapner/claude-code-basecamp --skill cost-speed-metergit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/benkapner/claude-code-basecamp/cost-speed-meter)<a href="https://agentmods.dev/skills/benkapner/claude-code-basecamp/cost-speed-meter"><img src="https://agentmods.dev/badge/skills/benkapner/claude-code-basecamp/cost-speed-meter.svg" alt="Measured on agentmods" 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.00047 | $0.01369 |
| Opus 5 | $0.00023 | $0.00685 |
| Sonnet 5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
cost-speed-meter 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost & Speed Meter
Track execution time. Suggest faster paths. Prove optimizations worked.
Every bash command is timed and stored. Across sessions, you see trends: is the test suite slower? Did that optimization help? Should you run unit tests instead of full integration tests for faster feedback?
When to Use
- User runs tests, builds, or lint commands — timing is tracked automatically
- User asks: "is this slow?", "how long did that take?", "what's the slowest operation?"
- User asks: "what's a faster way to do this?", "what's the quick feedback loop?"
- User is optimizing something — measure before, optimize, measure after to prove it worked
- Working across multiple repos — compare execution costs
What It Tracks
| Operation | Tracked? | Example |
|---|---|---|
pytest, jest, cargo test, go test |
✓ Tests | 45s |
npm run build, cargo build, pip install |
✓ Builds | 8s |
ruff check ., eslint ., cargo clippy |
✓ Lint | 2s |
git push, git pull |
✓ VCS | 3s |
| Custom commands | ✓ Named in .claude/metrics.json |
custom:deploy |
Output
Session Status (automatic)
After relevant commands, status line shows:
[METRICS: tests 45s | build 8s | slowest: integration tests]
Command Reports
On demand:
/metrics Show this session's measurements
/metrics-report Weekly summary (last 7 days, trends)
/metrics-slowest Which operations cost the most time
/metrics-recommend Suggest faster paths (unit tests vs integration)
Fast-Path Recommendations
Auto-detect patterns:
Full suite: pytest (45s)
Unit only: pytest -m 'not integration' (15s)
→ Recommendation: For quick feedback, use unit tests (3x faster)
Use full suite before pushing.
Per-language:
- Python:
pytest -m 'not slow',pytest tests/unit/ - Node:
npm run test:unit,vitest --run(vs jest) - Rust:
cargo test --lib(vs full + integration) - Go:
go test ./...(vsgo test ./... -vwith benchmarks)
What ships with it
2 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.
- yesterday Changed · -1 lines · -3 tokens per session 994d6606a9dd
- 5d ago First seen · 176 lines · 50 tokens per session scan A 4c8c05edc9f7
cost-speed-meter is a skill published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,369 once invoked, about $0.0002 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
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
pm-metrics
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked only — do NOT auto-trigger. Triggers on…
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…