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/radumarias/xorio-claude-plugin/guidegit clone --depth 1 https://github.com/radumarias/xorio-claude-pluginWrote 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/radumarias/xorio-claude-plugin/guide)<a href="https://agentmods.dev/commands/radumarias/xorio-claude-plugin/guide"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/guide.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.00014 | $0.03866 |
| Opus 5 | $0.00007 | $0.01933 |
| Sonnet 5 | $0.00003 | $0.00773 |
| Haiku 4.5 | $0.00001 | $0.00387 |
Grade A, and why
guide 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide Command
Interactive onboarding — detect project context, show available workflows, recommend a starting point, and launch chosen workflow.
Argument Parsing
Parse $ARGUMENTS. If a workflow name is provided, set DIRECT_MODE to that workflow name and skip Steps 2-3.
Valid workflow names (also accept common aliases):
tests(aliases:test,testing)polish(aliases:cleanup,clean)polish-auto(aliases:auto,auto-polish)review(aliases:code-review)build(aliases:feature,feature-dev)commit(aliases:commit-message)root-cause(aliases:rca,debug,5-whys)deps(aliases:check-deps,dependencies)review-pr(aliases:pr-review,ultra-review)mallware-check(aliases:malware,malware-check,scan)brainstorm(aliases:ideas,ideate)review-loop(aliases:audit,audit-loop)team-forming(aliases:form-team,team,compose-team)
Step 1: Context Detection (silent — never print raw output)
Run these commands and store the results internally:
git diff --stat HEAD
git branch --show-current
test -f Cargo.toml && echo "rust"
test -f package.json && echo "typescript"
test -f pyproject.toml && echo "python"
test -f setup.py && echo "python"
Extract:
CHANGES_COUNT: number of changed files (0 if clean)BRANCH: current branch nameLANGUAGES: list of detected languagesON_MAIN: true if branch ismainormaster
Step 2: Present Overview (skip if DIRECT_MODE)
Print the overview table and a context-based recommendation.
## xorio workflows
| # | Workflow | What it does | Command |
|---|----------|-------------|---------|
| 1 | Test | Analyze coverage gaps, detect anti-patterns, generate idiomatic tests | `/xorio:tests` |
| 2 | Polish | 9-step pipeline: simplify → cleanup → review → security audit → validate | `/xorio:polish` |
| 3 | Polish Auto | Autonomous polish loop — runs until clean or max iterations | `/xorio:polish --auto` |
| 4 | Review | Multi-agent review with user decision point — PR review → code review → simplify | `/xorio:review` |
| 5 | Build | Guided feature development — architecture analysis → implementation blueprint | `feature-dev:feature-dev` |
| 6 | Commit | Generate a conventional commit message from current changes (read-only) | `/xorio:commit-message` |
| 7 | Root Cause | 5 Whys analysis — trace a problem to its root cause | `/xorio:root-cause` |
| 8 | Check Deps | Verify required plugins and MCP servers are installed | `/xorio:check-deps` |
| 9 | Review PR | Deep multi-agent PR review — adversarial validation, verified fixes, looped to convergence | `/xorio:review-pr` |
| 10 | Malware Check | Recursive scan for malware, obfuscation, call-home, prompt injection | `/xorio:mallware-check` |
| 11 | Brainstorm | Multi-agent ideation — ideate across lenses → refute → debate → ranked report | `/xorio:brainstorm` |
| 12 | Review Loop | Multi-round audit loop — finders → adversarial verify → fix → repeat until dry | `/xorio:review-loop` |
| 13 | Team Forming | Compose & spawn an agent team for a task-group — architect plans + composes → plan-review gate → verification roles | `/xorio:team-forming` |
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 · 362 lines · 14 tokens per session scan A af53f38b814b
guide is a command published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 3,866 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.