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/implementgit 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.00095 |
| Opus 5 | $0.00000 | $0.00048 |
| Sonnet 5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
implement 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 implement — 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
/implement
Execute the canonical workflow: .agent/workflows/implement.md
Required reads before execution
.agent/rules/security_guardrails.md— auto-enforced during implementation- Active Work Log — must contain plan reference before proceeding
Execution
Follow every step in .agent/workflows/implement.md sequentially.
Minimal and reversible edits only. After changes, provide diff summary and evidence.
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 · 15 lines · 0 tokens per session scan A 08caf34eac6d
implement 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 95 tokens. A static security scan graded it A with 0 findings. It is 100% identical to implement, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
spec-research
需求 → 约束集（并行探索 + OPSX 提案）.
spec-design
Create comprehensive technical design for a specification.
color-palette
Generate an accessible colour palette from a hex value.
ux-extract
Exhaustively extract UX patterns from a reference web app into a reusable pattern library.
speckit.clarify
This project uses the GAIA preset. Bare /speckit-clarify is not the clarify path here: core clarify writes an off-shape artifact (a ## Clarifications / ### Session block with five-word answers) and carries a question cap GAIA does not use. Run /gaia-spec instead — it drives GAIA's coverage-based Socratic clarify loop…
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).