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/kbwen/agent-virtual-office/bootstrapgit clone --depth 1 https://github.com/KbWen/agent-virtual-officeWhat 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.00189 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
bootstrap 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.
This is a copy
100% identical to bootstrap — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/bootstrap
Execute the canonical workflow: .agent/workflows/bootstrap.md
Required reads before execution
.agent/rules/state_machine.md— phase transitions.agentcortex/context/current_state.md— SSoT
Execution
Follow every step in .agent/workflows/bootstrap.md sequentially.
The user's task description is: $ARGUMENTS
- Do NOT skip any steps.
- Per
AGENTS.md§3/§6: if the user's message explicitly requested a downstream phase (/plan,/implement,/review,/test,/ship, etc.) in the SAME message, proceed directly into that phase after the gate passes — no extra confirmation pause. - Otherwise (phase entry only inferred, no explicit downstream request), output the bootstrap report, then STOP and ask user for next step.
- End response with ⚡ ACX.
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 · 22 lines · 0 tokens per session scan A d134ab587bdc
bootstrap is a command published in the GitHub repository KbWen/agent-virtual-office (11 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 189 tokens. A static security scan graded it A with 0 findings. It is 100% identical to bootstrap, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
frontend
Injects context of all relevant cli files.
cleanup-back-to-main
Go back to main and clean up the branch.
spec-design
Create comprehensive technical design for a specification.
OPSX: Bulk Archive
Archive multiple completed changes at once.
result
Fetch the output of a finished background Antigravity (agy) job, then verify it.
consensus
Fan out, then run one arbiter pass that synthesizes a single verdict.