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/terrylica/cc-skillsWrote 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/terrylica/cc-skills/statusline-tools)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/statusline-tools"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/statusline-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
statusline-tools 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 2d 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
{
"name": "statusline-tools",
"description": "Custom status line with git status indicators",
"version": "30.1.0",
"source": "./plugins/statusline-tools",
"category": "utilities",
"author": {
"name": "Terry Li",
"url": "https://github.com/terrylica"
},
"keywords": [
"statusline",
"status-bar",
"git-status"
],
"strict": false
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 65 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
3 files beside marketplace.json#statusline-tools 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.
- 2d ago First seen · 17 lines scan A ad5892a5646e
statusline-tools is a plugin published in the GitHub repository terrylica/cc-skills (62 stars, last pushed yesterday), 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-09-05.
Other plugins, from other repositories
auto-stage
Automatic git staging for Claude Code. A PostToolUse hook on Edit|Write runs git add on every file Claude modifies, so git status always shows exactly what Claude touched and pre-commit review needs no manual staging. Files outside a git repo are skipped, .gitignore is respected (ignored files fail to stage and the.
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
github-workflows
PR finalization (single, repo-wide, or org-wide including bots), repo refresh, rebase-merge, merge, review thread resolution, issue shaping, issue sweeping that reconciles open issues against reality, and diagnosing silent GitHub Actions failures.
git-workflows
Git main branch synchronization, troubleshooting, and post-merge cleanup workflows.
git-standards
Git workflow standards, branch hygiene, PR creation guards, and issue linking.
contribute
Structured guide for open-source contribution: discover issues, analyze repos, write code, test, submit PRs, and respond to review feedback.