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.
git clone --depth 1 https://github.com/Yorha9e/moamcpWrote 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/yorha9e/moamcp/tower-boot)<a href="https://agentmods.dev/commands/yorha9e/moamcp/tower-boot"><img src="https://agentmods.dev/badge/commands/yorha9e/moamcp/tower-boot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/yorha9e/moamcp/tower-boot"><img src="https://agentmods.dev/badge/commands/yorha9e/moamcp/tower-boot.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00526 |
| Opus 5.5 | $0.00011 | $0.00210 |
| Sonnet 5.5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
tower-boot 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 1mo 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.
What it actually says
在当前或指定的 git 仓库启动 tower 工作流。$ARGUMENTS 为目标描述，可带可选的仓库绝对路径作为首 token（如 D:/path/to/repo 重构登录模块）；缺省路径取当前 Working Directory。执行步骤：
- 解析
$ARGUMENTS：首 token 是已存在的目录绝对路径则作为目标仓库，其余作为目标描述；否则整体作为目标描述，仓库取系统提示中当前 Working Directory 的绝对路径。$ARGUMENTS为空或目标描述缺失时，先向用户问清目标再继续，不要自己编造。 - 校验仓库：运行
git rev-parse --show-toplevel和git log --oneline -1，确认是 git 仓库且有 ≥1 个提交（boot 的硬性前提）。不满足则向用户报告原因并停止，不要尝试修补仓库。 - 用 Agent 工具派发
tower-orchestrator子代理，prompt 中写明：- 仓库根的绝对路径（它所有
mcp__plugin-moamcp_moamcp__moa_tower_*调用的workspace参数，不可相对化）； - 用户目标原文；
- 若仓库有明显的测试/构建命令（如 package.json 里的
npm test），作为ci_command候选建议给出，由 orchestrator 自行定夺； - 要求它先执行
moa_tower_boot注册塔台（tower_agent_id可省，自动按工作区匹配），再moa_tower_plan拆分 mission，之后按协议推进 spawn/register/review/merge，完成后moa_tower_teardown清理 worktree。
- 仓库根的绝对路径（它所有
- 主代理自身绝不直接调用任何
moa_tower_*工具——boot 会拒绝 main，roster 也不认未注册身份。后续查询进度、追加指令，一律 resume 同一个 tower-orchestrator 子代理实例转达。 - orchestrator 返回后，向用户汇报：分支名、mission 列表、各 worker/reviewer 分配和当前状态。
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.
- 1mo ago Changed d1884c63b34b
- 1mo ago Changed 6c64a0ca6a62
- 1mo ago First seen · 16 lines · 27 tokens per session scan A b1f8a03ffdc8
tower-boot is a command published in the GitHub repository Yorha9e/moamcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 526 once invoked, about $0.0001 per session on Opus 5.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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.