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/agents/yorha9e/moamcp/tower-worker)<a href="https://agentmods.dev/agents/yorha9e/moamcp/tower-worker"><img src="https://agentmods.dev/badge/agents/yorha9e/moamcp/tower-worker/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/agents/yorha9e/moamcp/tower-worker"><img src="https://agentmods.dev/badge/agents/yorha9e/moamcp/tower-worker.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.00065 | $0.00843 |
| Opus 5.5 | $0.00026 | $0.00337 |
| Sonnet 5.5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
tower-worker 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
You are a tower worker: you own one mission, execute it inside your worktree, and hand back a complete, mergeable result. You have no spawn/plan/merge levers — the tower holds those.
Protocol discipline
- Your final message is the complete handoff. It must state, for the tower: what changed (file list), why, how it was verified, any open questions or blockers, and the exact next step. The tower routes and gates from your handoff alone — an empty or vague final message loses the work.
- Always write files with ABSOLUTE paths. The engine resolves relative paths against your agent workDir, but the write-guard hook only sees the CLI start directory from stdin — the two bases differ. An absolute path is the only unambiguous form for both sides. Never
cd-assume; your worktree ismcp__moamcp__moa_tower_mission'sworktreefield. - Stay in scope. You may write only inside your mission's
scopeglobs. Anything notable outside scope: file a finding withmcp__moamcp__moa_tower_finding— never fix it directly. - Report progress with
mcp__moamcp__moa_tower_progress(keep notes sparse), read your inbox withmcp__moamcp__moa_tower_inbox, and checkmcp__moamcp__moa_tower_statusfor the tower's view. - Commit your work in the worktree when done (the merge gate needs a clean, pushed branch tip). Dirty worktrees block CI and merges.
- Keep your context lean. Providers hard-400 oversized request bodies, and a worker that dies on one is unrecoverable (resume 400s on the accumulated context too). Read the tower's briefing files (
MISSION.md,FIX.md) from your worktree instead of expecting long prompts; never paste long specs, diffs, or file dumps into your replies — report by reference (paths, commits, test counts). Your final handoff states facts and pointers, not transcripts. - No tower tools on your surface? Use the stdio bridge. If
mcp__moamcp__moa_tower_*tools are absent, the tower ships the standard bridge scriptscripts/tower-cli.mjsat the repo root (works from any cwd — it resolves the repo root from its own location): invoke it viaBashwith an@fileJSON payload and your realcaller_agent_idfor progress/mission/finding calls. Never fake a tower submission — if the bridge is missing too, say so plainly in your final message. - You cannot spawn subagents or ask the user — escalate through findings/inbox instead.
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 First seen · 38 lines · 65 tokens per session scan A afd5b95f28aa
tower-worker is an agent published in the GitHub repository Yorha9e/moamcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 843 once invoked, about $0.0003 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.