Claude Code Statusline

F 50 completed
Other
unknown / shell · tiny
6
Files
396
LOC
0
Frameworks
2
Languages

Pipeline State

completed
Run ID
#1544057
Phase
done
Progress
0%
Started
2026-04-16 22:28:28
Finished
2026-04-16 22:28:28
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
10.22
Framework unique
Isolation
Last stage change
2026-05-10 03:35:10
Deduplication group #47272
Member of a group with 954 similar repo(s) — canonical #1451475 view group →
Powered by Repobility — scan your code at https://repobility.com

AI Prompt

Create a command-line status line tool for Claude Code that displays real-time usage metrics directly from stdin. I need it to show the token usage percentage for a 5-hour window with a visual bar and time remaining. It should also display the context window usage percentage, color-coded as green, yellow, or red, and track the count of running, session-spawned, and total agents. Additionally, include a visual bar for the 7-day usage limit percentage. The tool must be built using shell scripting and Python 3 to parse the JSON payload from stdin.
shell bash python cli status-line terminal claude real-time json scripting
Generated by gemma4:latest

Catalog Information

Create a command-line status line tool for Claude Code that displays real-time usage metrics directly from stdin. I need it to show the token usage percentage for a 5-hour window with a visual bar and time remaining. It should also display the context window usage percentage, color-coded as green, yellow, or red, and track the count of running, session-spawned, and total agents. Additionally, include a visual bar for the 7-day usage limit percentage. The tool must be built using shell scripting

Tags

shell bash python cli status-line terminal claude real-time json scripting

Quality Score

F
49.9/100
Structure
52
Code Quality
45
Documentation
52
Testing
0
Practices
75
Security
92
Dependencies
60

Strengths

  • Consistent naming conventions (snake_case)
  • Good security practices — no major issues detected
  • Properly licensed project

Weaknesses

  • No tests found — high risk of regressions
  • No CI/CD configuration — manual testing and deployment

Recommendations

  • Add a test suite — start with critical path integration tests
  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a linter configuration to enforce code style consistency

Languages

shell
77.8%
markdown
22.2%

Frameworks

None detected

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/1367756.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV