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/AwesomeJun/CC-statuslineWrote 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/awesomejun/cc-statusline/cc-statusline)<a href="https://agentmods.dev/plugins/awesomejun/cc-statusline/cc-statusline"><img src="https://agentmods.dev/badge/plugins/awesomejun/cc-statusline/cc-statusline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/awesomejun/cc-statusline/cc-statusline"><img src="https://agentmods.dev/badge/plugins/awesomejun/cc-statusline/cc-statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
CC-statusline 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 1mo 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.
This is a copy
86% identical to awesome-statusline marketplace — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "awesome-statusline",
"version": "3.3.2",
"description": "A Claude Code statusline that shows reasoning effort (⚡) and thinking (💡). 5 presets (xsmall-xlarge), Catppuccin theme, no Node/Nerd Font, native PowerShell on Windows.",
"author": {
"name": "AwesomeJun",
"email": "[email protected]",
"github": "AwesomeJun"
},
"homepage": "https://github.com/AwesomeJun/CC-statusline",
"keywords": ["statusline", "catppuccin", "effort", "thinking", "context-window", "terminal"]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 12 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 1mo ago First seen · 13 lines scan A a4e78ee65dbf
CC-statusline is a plugin published in the GitHub repository AwesomeJun/CC-statusline (180 stars, last pushed 3mo 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. It is 86% identical to awesome-statusline marketplace, differing in 26 lines, and is treated as a copy.
Other plugins, from other repositories
aio-workflow
Author Workflow-tool scripts that spend effort like it's free and waste none of it. A maximal-effort playbook for multi-agent orchestration: pick an effort tier, then scale fan-out width, verification votes, and discovery rounds off it. Composes named amplifiers — multi-modal sweep, adversarial + perspective-diverse…
aio-catch-me-up
Turn Claude into a wise teacher that makes sure YOU deeply understand the work an AI agent just did — the problem, the solution, the design decisions, the edge cases, and why it matters. Incremental and mastery-gated: it has you restate your understanding first, fills the gaps at the depth you ask for (eli5 / eli14 /…
aio-code-review
Runs an adaptive, project-aware code-review workflow and carries Google's engineering code-review playbook it applies. The workflow profiles the project, detects its real lint/type-check/test tooling and house conventions, reviews on two tracks (mechanical + semantic 8-dimension rubric), adversarially verifies each…
aio-jev-hint
Author a UserPromptSubmit hook + .jev-hint catalog file that classifies every user prompt against a JSON catalog of {name, useWhen, context} entries via a batched LLM boolean-question call (Vercel AI SDK experimentalevaluate, model typesafe-ai/jev), then injects matched entries as additionalContext when confidence c.
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.
aio-monitoring-observability
Monitoring and observability strategy, implementation, and troubleshooting. Metrics design (Golden Signals, RED/USE), distributed tracing (OpenTelemetry), alerting, SLOs, dashboards, log aggregation, and tool selection. Includes 7 automation scripts and production-ready templates.