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/statusgit 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/status)<a href="https://agentmods.dev/commands/px0-ai/px0/status"><img src="https://agentmods.dev/badge/commands/px0-ai/px0/status.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.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
status 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
px0 status
Whether anything needs attention, in one screen.
Answering that used to take three commands: px0 daemon status for
whether the scheduler is alive, px0 runs list --failed for what went
wrong, and px0 doctor for whether the install is sound. This
assembles the parts of those that matter, and makes no network or model call, so
it is cheap enough to run whenever you wonder.
Implemented by px0/status.py.
px0 status [--hours N] [--json]
--hours N
How far back a failure still counts as news.
- Input: a whole number of hours.
- Default: 24.
px0 status --hours 72
--json
The same information as one object: daemon state, workflow counts, next fire times, recent runs, failures, the notification policy, and the problems found.
- Input: flag, no value. Default off.
px0 status --json | jq '.problems'
What it reports
| Line | What it tells you |
|---|---|
| scheduler | Whether the daemon is running, and on which platform |
| workflows | How many exist, are scheduled, are watched, are disabled |
| next | The next fire time per scheduled workflow, soonest first |
| runs | How many ran in the window, how many failed, how many are in flight |
| failures | Each failed run with its first line of error |
The problems it looks for
| Problem | Fix it prints |
|---|---|
| Workflows are scheduled but the daemon is not running | px0 daemon start |
| A run failed in the window | px0 runs why <run-id> |
A run failed and notify.on_failure is none |
px0 config set notify.on_failure desktop |
| A workflow file does not parse | px0 workflows validate |
Related configuration
| Key | Effect |
|---|---|
notify.on_failure |
Whether a failed run tells you anything. status flags it when failures happened and this is none |
logs.path |
Where the run records it reads live |
Exit codes
| Code | When |
|---|---|
0 |
Nothing needs attention |
1 |
At least one problem was found |
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.
- 3d ago First seen · 73 lines · 0 tokens per session scan A a212be1bd13d
status 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 529 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.