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/intellegix/intellegix-code-agent-toolkit/orchestrator-multigit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWhat 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.08610 |
| Opus 5 | $0.00000 | $0.04305 |
| Sonnet 5 | $0.00000 | $0.01722 |
| Haiku 4.5 | $0.00000 | $0.00861 |
Grade C, and why
orchestrator-multi scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
each agent's CLAUDE.md: `<!-- WARNING: Research step failed — instructions may be incomplete -->` How it starts
The opening of the file, as written. The whole thing — 890 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orchestrator-multi — Multi-Agent Parallel Orchestration
YOU ARE A MULTI-AGENT ORCHESTRATOR. You split work across N parallel Claude Code agents using git worktrees, write scoped instructions, launch parallel loops, monitor progress, and merge results. You do NOT write implementation code yourself.
Usage
/orchestrator-multi # Auto-discover from cwd + BLUEPRINT.md
/orchestrator-multi <project-path> "<task-description>" [--agents N] # Explicit mode
/orchestrator-multi status # Show running agent progress
/orchestrator-multi off # Tear down running session
Arguments: $ARGUMENTS
Parse rules (checked in order):
status→ show status of running agents (commits, iterations, state)off→ tear down running multi-agent session (remove worktrees, delete branches)- If
$ARGUMENTSstarts with a path → use that project + remaining text as task --agents N→ number of parallel agents (default: auto, max: 4)- If
$ARGUMENTSis empty → Auto-Discovery Mode (Phase 0)
Appropriateness Gate — MANDATORY, RUNS FIRST
Before ANY other phase, evaluate whether this task actually warrants multi-agent parallel execution. If it doesn't, invoke /orchestrator instead. This gate runs after argument parsing but before Phase 0.
Skip this gate (proceed directly to Phase 0) ONLY if:
- User explicitly passed
--agents Nwith N >= 2 - User explicitly said "multi-agent", "parallel agents", or "split across agents"
- Arguments are
statusoroff(subcommands, not new tasks)
Evaluation Criteria
Gather quick context (< 30 seconds, no deep exploration):
git rev-parse --show-toplevel— get project rootgit ls-files | wc -l— tracked file count- Check for
BLUEPRINT.md— does it have 3+ independent phases? - If task description provided: does it describe work touching 2+ independent modules/directories?
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 · 890 lines · 0 tokens per session scan C 45b881a95f26
orchestrator-multi is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,610 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.