Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tidybot-services/tidybot-universe/xbot-server)<a href="https://agentmods.dev/commands/tidybot-services/tidybot-universe/xbot-server"><img src="https://agentmods.dev/badge/commands/tidybot-services/tidybot-universe/xbot-server.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.1 | $0.00000 | $0.00695 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade C, and why
xbot-server scanned grade C with 2 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 8d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
IdentityFile ~/.ssh/id_ed25519 Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sleep 10 && curl -s http://localhost:8090/health How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/xbot-server — Set up remote service server access
Initialize the service catalog to discover ML services on a remote GPU server.
Usage
/xbot-server
What to do
-
Ask the user for server configuration. Use AskUserQuestion to collect:
- Server IP — the remote GPU server address (e.g.,
192.168.1.100) - SSH username — the user account on the server (e.g.,
gpu_user) - Service directory — the directory on the server containing deployed services (e.g.,
/home/gpu_user/services)
Ask all three in one AskUserQuestion call. Do NOT hardcode or assume any values.
- Server IP — the remote GPU server address (e.g.,
-
Set up SSH access. Test connectivity:
ssh -o ConnectTimeout=5 -o BatchMode=yes USERNAME@SERVER_IP "echo connected"If it fails, ask the user to run
ssh-copy-id USERNAME@SERVER_IPinteractively:! ssh-copy-id USERNAME@SERVER_IPThen verify again.
-
Add SSH config alias (if not already present). Add an entry to
~/.ssh/config:Host service-server HostName SERVER_IP User USERNAME IdentityFile ~/.ssh/id_ed25519 -
Run the setup script. Execute:
cd ~/tidybot_uni/Tidybot-Universe/service-server-setup bash setup.sh --server-ip SERVER_IP --username USERNAME --service-dir SERVICE_DIRThis will:
- Verify SSH connectivity
- Verify the service directory exists
- Write
config.json - Run an initial scan to discover services
-
Start the catalog server. Launch in the background:
cd ~/tidybot_uni/Tidybot-Universe/service-server-setup python3 service_scanner.py &Wait for it to be ready:
sleep 10 && curl -s http://localhost:8090/health -
Show discovered services. Fetch and display the catalog:
curl -s http://localhost:8090/servicesFormat the output as a clear table for the user showing:
- Service name
- Port
- Status (running/stopped)
- URL
- Number of endpoints
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.
- 8d ago First seen · 97 lines · 0 tokens per session scan C 53cb71537593
xbot-server is a command published in the GitHub repository TidyBot-Services/Tidybot-Universe (56 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 695 tokens. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.