Track the carbon footprint of your Claude Code sessions
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
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 unknown. 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 claude-carbon 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/gwittebolle/claude-carbon ~/.claude/commands/claude-carbonRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/commands/claude-carbonNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ │ └─ claude-carbon/ ← installs here ├─ agents/ └─ settings.json
Track the carbon footprint of your Claude Code sessions