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/xflowgit 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.00008 | $0.00117 |
| Opus 5 | $0.00004 | $0.00059 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
xflow 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
/xflow - Orchestrated Work
- Use orchestrateX module 08 to explore repository facts, then run socratesX for unresolved user decisions.
- Ask all unresolved questions from the current analysis phase in one batch; offer options only for real trade-offs.
- Present one Ready Summary confirmation gate, then generate or update the Hybrid Tree.
- Dispatch implementation work by dependency order.
- Trigger evaluatorX where the workflow requires independent testing review.
- Keep the final repair and completion decision with the Main Agent.
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 · 13 lines · 8 tokens per session scan A 6eeda4e9a36a
xflow is a command published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 117 once invoked, about $0.0000 per session on Opus 5. 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.