A stop-loss for Claude Code: detects loops, compaction danger, failed tools, and token waste before the next request.
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 71/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if cc-blackbox belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/softcane/cc-blackbox && cd cc-blackbox && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf cc-blackboxNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ cc-blackbox/ ← clones here
A stop-loss for Claude Code: detects loops, compaction danger, failed tools, and token waste before the next request.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: June 18, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.