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 commands/si-ic/backlog-skill/statusline-uninstallgit clone --depth 1 https://github.com/SI-IC/backlog-skillWrote 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/si-ic/backlog-skill/statusline-uninstall)<a href="https://agentmods.dev/commands/si-ic/backlog-skill/statusline-uninstall"><img src="https://agentmods.dev/badge/commands/si-ic/backlog-skill/statusline-uninstall.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.00051 | $0.00217 |
| Opus 5 | $0.00026 | $0.00109 |
| Sonnet 5 | $0.00010 | $0.00043 |
| Haiku 4.5 | $0.00005 | $0.00022 |
Grade B, and why
statusline-uninstall scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: Remove the backlog badge from the Claude Code statusLine. Restores your previous statusLine command if there was one, or removes the statusLine entirely; deletes the wrapper script. Edits ~/.claude/settings. What it actually says
Below is the engine's output for the statusLine rollback. The raw output is NOT shown to the user: it is injected into your context only. The user sees only what you print in this reply.
Relay the result faithfully: whether the previous command was restored, whether the statusLine was removed entirely, or whether it turned out to be someone else's and was left untouched. Say that the change takes effect in a new Claude Code session.
If the output starts with error: — show the error text and do not claim success.
!python3 "${CLAUDE_PLUGIN_ROOT}/scripts/backlog.py" statusline uninstall 2>&1 || true
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.
- 5d ago First seen · 18 lines · 51 tokens per session scan B a68c251b6180
statusline-uninstall is a command published in the GitHub repository SI-IC/backlog-skill (1 stars, last pushed 13d ago), licensed MIT. It adds 51 tokens to every session and 217 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
init
Multi-agent codebase audit that GENERATES the audit manifest (phases/tasks) at manifestPath. Interviews you for scope/goals, fans out parallel read-only explorers, synthesizes findings, then presents the proposed phases for approval BEFORE writing — approve to materialize, or park them as proposals for later…
panel
Audit pipeline: open / stop / check a local control-panel UI to visually manage .claude/audit.config.json and the manifest's composition levers (reviewSkill, per-task skills/models, buildCommands) — with live validation and discovery of the skills & agents available in this repo + globally. Ephemeral, on-demand; a…
layout
Audit pipeline: choose how the manifest is stored — sharded (an index plus one file per phase: fewer tokens per phase run, parallel-safe across worktrees) or single-file (one file, one diff, no index). A layout CHOICE, not a version upgrade: both shapes are current, neither goes out of date, and this command moves in…
logs
Audit pipeline: prune the local feeds this plugin writes under logsDir — today the plan-gate events feed rendered by the panel Plan gate card. Removes rows that no longer belong (paths outside this repository, lines that are not JSON, optionally rows past an age you name), prints what went and what stayed, and never…
usage
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).