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/storegit 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/store)<a href="https://agentmods.dev/commands/px0-ai/px0/store"><img src="https://agentmods.dev/badge/commands/px0-ai/px0/store.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.01681 |
| Opus 5 | $0.00000 | $0.00840 |
| Sonnet 5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
store scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
px0 store
The store as a whole: everything px0 knows, in one directory.
Implemented by px0/store.py.
px0 store list
px0 store export <dir>
px0 store import <dir> [--merge] [--force]
px0 store path [--json]
px0 store verify [--json]
px0 store list
Workflows, guidelines, and brain files in one pass, each under its own heading.
- Arguments: none.
- The same printers as
px0 workflows list,px0 guidelines list, andpx0 brain list. A single-entity listing prints no heading, because the command you typed already said what you are looking at.
px0 store list
px0 store export
Copy the store's content and version history somewhere else — the supported way to move a store to another machine.
dir (required)
Where to write the export.
- Input: a directory path. Created if it does not exist.
px0 store export ~/backups/px0-2026-08-21
What is included
workflows/, guidelines/, brain/, output/, config.toml, and
the parts of .state/ that matter for continuity: version history, the schema
marker, and the schedule.
What is excluded
Credentials, deliberately and thoroughly:
.state/credentials.tomlis not copied.config.tomlis exported with every secret key blanked.config.toml's version history is dropped, and the blobs only it referenced are deleted.
That last point is the one that matters: the Composio key is written to
config.toml, and config.toml is versioned, so redacting only the live file
would leave the key one change-log entry away. Both are scrubbed, or
"credentials excluded" would be a false promise.
The retrieval index is not exported. Run px0 brain reindex after importing.
px0 store sync
Bring this store and a shared folder into line, on more than one machine.
export and import copy a whole store, which is the right answer once —
setting up a second machine — and the wrong answer every time after, because it
overwrites. So people pointed Dropbox at ~/.px0 instead, and that has a
specific, quiet failure: the version history is a SQLite database, and two
machines writing it produce a file that is neither machine's history. Nothing
notices until a revert needs it.
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.
- 4d ago First seen · 210 lines · 0 tokens per session scan A d7d34eda0801
store is a command published in the GitHub repository px0-ai/px0 (241 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,681 tokens. A static security scan graded it A with 0 findings. 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.
README
This folder gathers the project's 9 slash commands in a single place. Each command file specifies its traversal pattern (which Layer × Cycle cells it passes through, and in which cycle-stage flow) plus the Human Reviewer Gate. The nature of each role and the Layer × Cycle matrix have their SoT in…
wiki-discover
Discover unexpected connections in the LLM Wiki (Memex serendipity).
wiki-news
Search for latest news related to the LLM Wiki's key topics.
wiki-query
Query the LLM Wiki and synthesize an answer.
wiki-export
Export wiki to merged files for Claude.ai Project Knowledge.