by loadbalance-sudachi-kun · AI Tool · ★ 55
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
git clone https://github.com/loadbalance-sudachi-kun/claude-code-statusline.gitTaken from the project's README on GitHub. Check the security audit before running it.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 55 |
| Forks | 3 |
| Language | Shell |
| Category | AI Tool |
| License | MIT |
| Quality Score | 58/100 |
| Last Updated | 2026-03-08 |
| Created | 2026-03-05 |
| Platforms | claude-code, cli |
| Est. Tokens | ~3k |
Claude Code Statusline Claude Code のステータスラインに、モデル情報・コンテキスト使用率・セッションコストをリアルタイム表示するシェルスクリプトです。 このスクリプトは すてぃお(@suthio) さんの記事を参考に作成しました。詳しい仕組みや背景の解説はこちらをご覧ください： Claude Codeのステータスラインに使用率を出す 2つのバージョン statusline-command.sh（推奨） Claude Code が stdin で提供するデータのみを使用します。外部 API 呼び出しやキーチェーンアクセスは一切行いません。 statusline-command-with-usage.sh 5時間 / 7日間のレートリミット使用率をリアルタイム表示します。リセット時刻も併記されるため、いつ制限が解除されるかが一目でわかります。 ⚠️...
Looking for a claude-code-statusline alternative? If you're comparing claude-code-statusline with other ai tool tools, these 3 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
Skip to content github / docs Code Issues 80 Pull requests 35 Discussions Actions Projects 2 Security Insights
Skill to talk to Claude about your projects over the phone
.NET MAUI skills for GitHub Copilot and Claude Code
Explore other popular ai tool tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: