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/treex-x/workflowx/xstatusgit clone --depth 1 https://github.com/TreeX-X/WorkFlowXWhat 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.00274 |
| Opus 5 | $0.00000 | $0.00137 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
xstatus 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 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.
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.
What it actually says
Executed by Main Agent directly. Scan the project, collect workflow state, and generate an HTML status report.
User input: $ARGUMENTS
Syntax
/xstatus # Analyze current workflows, output to ./status-report.html, open in browser
/xstatus --output <path> # Specify custom output path, still opens in browser after generation
description: Generate huashu-styled HTML status report for workflow state
Execute inline (reading orchestrateX Module 07 / modules/07-status-report.md content directly):
Mode: xstatus
Arguments: $ARGUMENTS
Generate huashu-styled HTML status report:
- Parse arguments: --output (default: ./status-report.html)
- Scan .hybrid/ for Parent and Child documents
- Parse the lightweight registry, scope, dependencies, status, and verification notes
- Classify active work as xdo, xdel, or xflow when the mode is recorded
- Render huashu-styled HTML: hero, Children progress, issue heatmap, dependency graph
- Write to output path + auto-open in browser
Constraints:
- Read-only (no code/doc modifications)
- Idempotent (overwrite ./status-report.html)
- Empty sections hidden
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 · 35 lines · 0 tokens per session scan A 92a3694bc743
xstatus is a command published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 274 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
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
tutorial
Command "tutorial" from usurahi-project/usurahi, covering /tutorial, すること, 案内する要点 and 出力方針.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.