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-install)<a href="https://agentmods.dev/commands/labzink/cc-probeline/cc-probeline-install"><img src="https://agentmods.dev/badge/commands/labzink/cc-probeline/cc-probeline-install.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.00024 | $0.01014 |
| Opus 5 | $0.00012 | $0.00507 |
| Sonnet 5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade D, and why
cc-probeline-install scanned grade D with 3 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 Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The binary can wire itself into `~/.claude/settings.json`: 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install cc-probeline: /cc-probeline-install
Installs (or updates) the cc-probeline binary and wires it into the Claude Code status line. The plugin itself ships only commands and a status-line wizard — the compiled binary is delivered through a package manager (Homebrew / Scoop) or a signed install script. This command picks the right channel for the user's OS, shows the exact command, and runs it only after the user approves the native Bash permission prompt. Never install anything silently.
Usage
/cc-probeline-install
No arguments.
Step 0 — Detect current state
Run these and read the results:
command -v cc-probeline && cc-probeline --version
cc-probeline --check
Decide the mode:
- Not found in PATH → this is a fresh install. Go to Step 1.
- Found,
--checksays installation OK → already installed and wired. Tell the user it is already set up, show the version, and offer an update (Step 1 with the upgrade variant) or stop if they decline. - Found, but
--checkreports the status line is not wired → binary is present, only wiring is missing. Skip to Step 3.
Step 1 — Detect platform and package manager
uname -s; command -v brew; command -v scoop
Darwin/Linux→ prefer Homebrew ifbrewexists, otherwise the install script (Step 2c).- Windows (no
uname, orMINGW/MSYS/CYGWIN) → use Scoop (Step 2b).
Step 2 — Install (or update) the binary
Pick exactly one channel. Show the user the exact command first, then run it via the Bash tool — the Bash permission prompt is the user's explicit "yes, run this". Do not chain extra commands into the same call; keep the install command alone so the prompt is readable.
2a — Homebrew (macOS / Linux)
Install:
brew install --cask labzink/homebrew-tap/cc-probeline
Update:
brew upgrade --cask labzink/homebrew-tap/cc-probeline
After a Homebrew install/upgrade the binary is on PATH but the status line is not wired yet → continue to Step 3.
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 · 135 lines · 24 tokens per session scan D 15c545ae3756
cc-probeline-install is a command published in the GitHub repository labzink/cc-probeline (11 stars, last pushed 26d ago), licensed MIT. It adds 24 tokens to every session and 1,014 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, 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.