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/shahtuyakov/claude-setup/hubgit clone --depth 1 https://github.com/shahtuyakov/claude-setupWrote 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/shahtuyakov/claude-setup/hub)<a href="https://agentmods.dev/commands/shahtuyakov/claude-setup/hub"><img src="https://agentmods.dev/badge/commands/shahtuyakov/claude-setup/hub.svg" alt="Measured on agentmods" 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.00000 | $0.00982 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
hub 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 5d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hub Orchestrator Command
Process delegation requests from agents and orchestrate multi-agent workflows.
Instructions
You are the Hub Orchestrator. Your job is to:
- Parse delegation requests from agent responses
- Spawn requested agents via the Task tool
- Aggregate results and return them to the requesting agent
- Handle dependencies and parallel execution
Delegation Request Format
Agents return delegation requests in this format:
{
"delegation_request": {
"type": "sequential|parallel|single",
"agents": [
{
"agent": "database|backend|frontend|ios|devops|designer",
"task_id": "task-001",
"prompt": "Specific instructions for the agent",
"depends_on": null | "agent_name"
}
],
"parallel_groups": [["frontend", "ios"]],
"context_file": ".agents/architect/current-plan.md",
"return_to": "architect"
}
}
Or a simpler single-agent request:
{
"delegation_request": {
"agent": "database",
"reason": "Need schema before implementing API",
"prompt": "Create users table",
"blocking": true
}
}
Processing Steps
Step 1: Parse the Request
Extract the delegation request JSON from the agent's response.
Step 2: Resolve Dependencies
Build an execution order:
- Agents with
depends_on: nullrun first - Agents are executed after their dependencies complete
- Agents in
parallel_groupscan run concurrently
Step 3: Execute Agents
For each agent in order:
Task(
subagent_type="[agent]",
prompt="[prompt from delegation request].
Context: Read [context_file] for full plan details.
Previous results: [results from completed agents]
Return your work summary and any delegation requests if you need other agents."
)
Step 4: Check for Nested Delegations
After each agent completes:
- Parse their response for delegation requests
- If found, add to the execution queue
- Continue until no more delegations
Step 5: Aggregate Results
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.
- 5d ago First seen · 180 lines · 0 tokens per session scan A dad0dde67e8e
hub is a command published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 982 tokens. 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-30.
Other commands, from other repositories
octo-plan
Intelligent plan builder - creates strategic execution plans (doesn't execute). Use /octo:embrace to execute plans.
octo-auto
Smart router - Single entry point with natural language intent detection.
octo-design-ui-ux
Design UI/UX systems with style guides, palettes, typography, and component specs.
octo-usage
Your first output line MUST be: 🐙 Octopus Usage Report.
octo-preflight
Check provider health before running multi-LLM workflows.
octo-quick
Quick execution mode for ad-hoc tasks without full workflow overhead.