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/px0-ai/px0/uninstallgit clone --depth 1 https://github.com/px0-ai/px0Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/px0-ai/px0/uninstall)<a href="https://agentmods.dev/commands/px0-ai/px0/uninstall"><img src="https://agentmods.dev/badge/commands/px0-ai/px0/uninstall.svg" alt="Measured on agentmods" height="20"></a>What 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.00464 |
| Opus 5 | $0.00000 | $0.00232 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade C, and why
uninstall scanned grade C 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
deliberately leaving the store behind and telling you to run `rm -rf ~/.px0` What it actually says
px0 uninstall
Stop the daemon, remove its scheduler unit, delete the entire store, and uninstall the px0 package itself. This is the one command that removes px0 completely rather than changing what it does.
Implemented by px0/cli.py, reusing px0/daemon.py's uninstall and
px0/update.py's install-mechanism detection.
px0 uninstall [--yes]
What it does
- Stops the running daemon and removes its scheduler unit (the same as
px0 daemon uninstall). - Deletes the store at
PX0_HOME(~/.px0by default) — every workflow, guideline, brain file, credential, run record, and version history. - Uninstalls the px0 package itself, via
pipxorpip, whichever installed it.
Each step only runs if there is something to do: a store that was never initialized is skipped, and the package step still runs even without a store.
Options
--yes
Skip the confirmation.
- Input: flag, no value. Default off.
- Without it,
px0 uninstallprints exactly what it is about to do and asks once before touching anything. There is no partial undo: once the store is deleted, only a backup made withpx0 store exportcan bring it back.
px0 uninstall
px0 uninstall --yes
Relationship to install.sh --uninstall
install.sh --uninstall stops at the package and the scheduler unit,
deliberately leaving the store behind and telling you to run rm -rf ~/.px0
yourself. px0 uninstall is the same operation carried the rest of the way:
it removes the store too, with a confirmation in between.
Exit codes
| Code | When |
|---|---|
0 |
Uninstalled, or cancelled at the confirmation |
1 |
The confirmation could not be asked (no terminal, no --yes), or the package uninstall failed |
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.
- 5d ago First seen · 58 lines · 0 tokens per session scan C a7973af53954
uninstall is a command published in the GitHub repository px0-ai/px0 (246 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
wiki-ingest
Ingest a source document into the LLM Wiki.
wiki-discover
Discover unexpected connections in the LLM Wiki (Memex serendipity).
wiki-query
Query the LLM Wiki and synthesize an answer.
wiki-export
Export wiki to merged files for Claude.ai Project Knowledge.
wiki-trail
Create, follow, or list associative trails in the LLM Wiki (Memex trail-blazing).
wiki-lint
Command "wiki-lint" from alfadur7/llm-wiki-newsroom, covering traversal pattern, sub-procedure (owned by this folder), chain execution obligation, group structure and check items (full suite layout).