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.
/plugin marketplace add labzink/cc-probelinenpx agentmods add plugins/labzink/cc-probeline/marketplacegit 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/plugins/labzink/cc-probeline/marketplace)<a href="https://agentmods.dev/plugins/labzink/cc-probeline/marketplace"><img src="https://agentmods.dev/badge/plugins/labzink/cc-probeline/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cc-probeline marketplace 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 4d 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-marketplace.json",
"name": "cc-probeline",
"owner": {
"name": "Konstantin Labzin",
"email": "[email protected]"
},
"description": "Status line upgrade for Claude Code: tokens, cost, quota and subagents at a glance.",
"plugins": [
{
"name": "cc-probeline",
"source": {
"source": "github",
"repo": "labzink/cc-probeline"
},
"description": "Status line upgrade for Claude Code: live tokens, approximate session cost, quota warnings, active subagents.",
"version": "0.1.5",
"author": {
"name": "Konstantin Labzin",
"email": "[email protected]"
},
"homepage": "https://github.com/labzink/cc-probeline",
"repository": "https://github.com/labzink/cc-probeline",
"license": "MIT",
"keywords": ["statusline", "claude-code", "tokens", "cost", "quota", "observability"],
"category": "statusline"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
2 files beside marketplace.json 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.
- 4d ago First seen · 30 lines scan A 9a54fbf989b1
cc-probeline marketplace is a plugin published in the GitHub repository labzink/cc-probeline (11 stars, last pushed 22d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
super-token-saver
45% cost reduction measured. Cache expiry prevention, SubTask auto-delegation, zero-cost context restoration, real-time cost dashboard. The only Claude Code plugin built from CC source analysis.
claudetop marketplace
htop for your Claude Code sessions.
claudetop
htop for your Claude Code sessions — real-time cost tracking, cache efficiency, model comparison, smart alerts, web dashboard, and session analytics.
ccbar
Cost and quota statusline plugin for Claude Code.
claude-code-cost
See your Claude Code spend in USD per project, per git branch, and over time (by day, week, month), computed locally by reading the session logs Claude Code already writes to /.claude/projects. Never touches API traffic. Zero key, zero prompts, zero latency.
@vk0/agent-cost-mcp
Local-first Cost Guard for Claude Code. Per-tool ROI, subagent-tree attribution, anomaly detection, forecasts, and budget guardrails from local JSONL session logs. Complements native /cost and ccusage. Zero cloud, no API key.