Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/cnaught-inc/claude-code-plugins/uninstallgit clone --depth 1 https://github.com/CNaught-Inc/claude-code-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00458 |
| Opus 5 | $0.00000 | $0.00229 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade B, and why
uninstall scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. In `<projectPath>/.claude/settings.local.json`: What it actually says
/carbonlog:uninstall
Uninstall the CNaught Carbonlog plugin.
Instructions
Step 1: Confirm with the user
Use the AskUserQuestion tool to confirm: "This will remove all carbon tracking data and the plugin configuration. Continue?"
- If no: Stop here.
- If yes: Continue.
Step 2: Run the uninstall script
npx -y bun ${CLAUDE_PLUGIN_ROOT}/src/scripts/carbonlog-uninstall.ts
This removes all sessions and deletes the database.
Step 3: Clean up settings
Read ~/.claude/plugins/installed_plugins.json to find all carbonlog@cnaught-plugins entries and their projectPath values.
For each entry that has a projectPath:
- In
<projectPath>/.claude/settings.local.json:- If there is a
_carbonlogOriginalStatusLinekey, restore it as thestatusLinevalue and remove the_carbonlogOriginalStatusLinekey. - Otherwise, if the
statusLineconfig'scommandcontainscarbonlog-statuslineorstatusline-wrapper, remove thestatusLinekey. - Remove
"carbonlog@cnaught-plugins"from theenabledPluginsobject. IfenabledPluginsis empty after removal, remove the key entirely.
- If there is a
Then clean up global settings:
- In
~/.claude/settings.json: apply the same statusLine cleanup logic (restore original or remove carbonlog statusline). Remove"carbonlog@cnaught-plugins"fromenabledPlugins. - In
~/.claude/settings.local.json: remove"carbonlog@cnaught-plugins"fromenabledPluginsif present. - Remove all
carbonlog@cnaught-pluginsentries from~/.claude/plugins/installed_plugins.json.
Step 4: Confirm completion
Let the user know the uninstall is complete and that they can re-install at any time by installing the plugin and running /carbonlog:setup.
Notes
- Always use the
AskUserQuestiontool when asking the user a question with multiple choices.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 44 lines · 0 tokens per session scan B 2f715748728b
uninstall is a command published in the GitHub repository CNaught-Inc/claude-code-plugins (5 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 458 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.