Static source analysis that generates deterministic Claude Code documentation ecosystems — no LLM guessing, only code...
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 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if claudeos-core 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/claudeos-core/claudeos-core ~/.claude/commands/claudeos-coreRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/commands/claudeos-coreNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ │ └─ claudeos-core/ ← installs here ├─ agents/ └─ settings.json
Static source analysis that generates deterministic Claude Code documentation ecosystems — no LLM guessing, only code-confirmed facts.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: May 4, 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.