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/labzink/cc-probelineWrote 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/labzink/cc-probeline/cc-probeline-update)<a href="https://agentmods.dev/commands/labzink/cc-probeline/cc-probeline-update"><img src="https://agentmods.dev/badge/commands/labzink/cc-probeline/cc-probeline-update.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.00023 | $0.00608 |
| Opus 5 | $0.00012 | $0.00304 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade C, and why
cc-probeline-update scanned grade C with 2 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 7d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/labzink/cc-probeline/main/scripts/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/labzink/cc-probeline/main/scripts/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update cc-probeline: /cc-probeline-update
Updates cc-probeline to the latest release through whichever channel fits this machine (Homebrew / Scoop / install script). If it isn't installed yet, this same command installs it. Always show the exact command and run it only after the user approves the Bash permission prompt — never silently.
Keep it simple: detect the channel, run one update command, report the result. Do not investigate config files, caches, state, or why an update hint appeared — just update. If the tool is already on the latest version, say so and stop. Do not re-run the same command hoping for a different result.
Step 1 — Pick the channel
command -v brew scoop
brewpresent → Homebrew (2a)scooppresent (Windows) → Scoop (2b)- neither → install script (2c) — the default on Linux/macOS
Step 2 — Run one command (pick the matching channel)
Show the command, then run it via Bash so the permission prompt is the user's "yes".
2a — Homebrew
brew upgrade --cask labzink/homebrew-tap/cc-probeline || brew install --cask labzink/homebrew-tap/cc-probeline
Then, only if it was a brand-new install (status line not wired yet):
cc-probeline install --merge-settings
2b — Scoop (Windows)
scoop update cc-probeline || { scoop bucket add labzink https://github.com/labzink/scoop-bucket; scoop install cc-probeline; }
Then, only on a brand-new install:
cc-probeline install --merge-settings
2c — Install script (default — Linux/macOS, no package manager)
One command handles upgrade, fresh install, already-latest, and status-line wiring:
curl -fsSL https://raw.githubusercontent.com/labzink/cc-probeline/main/scripts/install.sh | sh
If it prints already the latest version, you are done — report that and stop.
Step 3 — Report (one line)
State the installed version and whether it was an upgrade, a fresh install,
or already up to date. The new version applies on the next status-line refresh
or in new Claude Code sessions. Mention that /cc-probeline-config customises rows,
colour, probes and display mode. If a command fails, show the exact error and
stop — do not retry blindly.
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.
- 7d ago First seen · 72 lines · 23 tokens per session scan C ad925bcb33e1
cc-probeline-update is a command published in the GitHub repository labzink/cc-probeline (11 stars, last pushed 26d ago), licensed MIT. It adds 23 tokens to every session and 608 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
dashboard
Open the claudetop web dashboard showing spending charts and session history.
export
Export Claude Code session history as CSV or JSON.
pricing
Update Claude model pricing to latest rates.
stats
Show Claude Code spending analytics (today/week/month/all/tag/branch).
branch
Show Claude Code costs per git branch / PR.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.