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/elasticdotventures/_b00t_/b00tgit clone --depth 1 https://github.com/elasticdotventures/_b00t_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/elasticdotventures/_b00t_/b00t)<a href="https://agentmods.dev/commands/elasticdotventures/_b00t_/b00t"><img src="https://agentmods.dev/badge/commands/elasticdotventures/_b00t_/b00t.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.00020 | $0.00155 |
| Opus 5 | $0.00010 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
b00t 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 17 lines · 20 tokens per session scan A 2c58544f40ac
b00t is a command published in the GitHub repository elasticdotventures/_b00t_ (14 stars, last pushed yesterday), with no licence file. It adds 20 tokens to every session and 155 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-30.
Other commands, from other repositories
remote-autopilot-install.v1
Remotely install Stakpak Autopilot on any reachable Linux host over SSH, with optional AWS/GCP/Azure VM discovery or provisioning: /remote-autopilot-install.
sprint
Ultrathink to generate the next VibeSolver project sprint using this streamlined approach.
article
Ultrathink to review the latest sprint based code generated and then write an article in first person style as step-by-step tutorial to evaluate the released features as a casual user, as a power user, and as a developer using VibeSolver. Write the article in markdown starting at level 2 heading with valid markdown…
develop
Read the sprints/ folder to identify the latest sprint. Review the product code generated so far. Continue developing the product based on the latest spring plan. If roadmap features were completed then mark them completed in specs/roadmap.md.
readme
Create or update the README.md of VibeSolver product. Review the existing README.md if available. Update or write it based on project code, sprints/ folder, specs/ folder, and articles/ folder. Create or update the README.md using similar style as popular GitHub repos.
test
Run comprehensive tests for this project. Fix any issues.