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 skills add koolamusic/claudefiles --skill towergit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/skills/koolamusic/claudefiles/tower)<a href="https://agentmods.dev/skills/koolamusic/claudefiles/tower"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/tower/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/skills/koolamusic/claudefiles/tower"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/tower.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.00063 | $0.01139 |
| Opus 5.5 | $0.00025 | $0.00456 |
| Sonnet 5.5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
tower 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 26d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tower
The orchestrator skill decides who does what. This skill decides where they run: one Herdr pane per child, visible to the user, instead of invisible background subagents.
Gate first:
test "${HERDR_ENV:-}" = 1
If the check fails, say the session is not inside Herdr and fall back to the
orchestrator's own substrate. Do not run any herdr command.
Commands
tower on— orchestrator mode with this substrate. Loadsorchestratorandherdrif they are not already in context.tower off— same asorchestrator off.tower status— the orchestrator status check, with pane states from Herdr.
What stays the same
Everything the orchestrator skill defines: the three slots, personas, routing
rules, the delegation brief, the war room table, the stall cap, and the safety
rules. Read them there. This file replaces only the "Child Agent Substrate"
section. The herdr skill remains the authority for CLI syntax and safety.
Substrate mapping
| Orchestrator step | Tower |
|---|---|
| Spawn a child | pane split (or tab create for an executor), then agent start <name> --kind claude --pane <id> |
| Continue a child | agent prompt <name> "<text>" --wait --timeout <ms> |
| Status check | agent list; per child agent get <name> |
| Read a closeout | agent read <name> --source recent-unwrapped --lines 200 |
| Worktree isolation | worktree create --branch <name> for the executor's workspace |
| Stall | agent_status unchanged across two status checks |
Naming
The agent name is the war room key: <branch-or-key>-<slot>, lowercase,
hyphens, under 32 chars. auth-exec, auth-audit, search-survey. The name
follows the pane occupant, so the same child answers follow-up prompts on that
branch, and agent list reads as the roster.
Placement
- Surveyors and auditors are short-lived: split beside the calling pane with
--no-focus, right when wide, down when tall, and close the pane after the closeout is recorded. - Executors are long-lived and own a branch: give each its own tab, labelled with the branch, so its transcript is not fighting for space. Use a worktree workspace when two executors are mutating at once.
- Never create a workspace, tab, or pane the user did not ask for beyond these rules, and never close one this session did not create.
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.
- 26d ago First seen · 114 lines · 63 tokens per session scan A 55dff45d2227
tower is a skill published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 1,139 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-09-22.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.