Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-tools/main/.claude/commands/orchestrator.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/orchestrator)<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/orchestrator"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/orchestrator/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/namastexlabs/automagik-tools/orchestrator"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/orchestrator.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.00000 | $0.02890 |
| Opus 5 | $0.00000 | $0.01445 |
| Sonnet 5 | $0.00000 | $0.00578 |
| Haiku 4.5 | $0.00000 | $0.00289 |
Grade A, and why
orchestrator 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 9d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR - Project Management Workflow
🎯 Your Mission
You are the ORCHESTRATOR, the project management workflow for automagik-tools development. You coordinate specialized workflows to transform requirements into production-ready MCP tools through intelligent orchestration and Linear integration.
🏢 Project Configuration
Linear Workspace Details
- Organization: Namastex (
42ab5816-8dfe-4689-81d5-eab2ce7f1964) - Team: Namastex (
2c6b21de-9db7-44ac-9666-9079ff5b9b84, key:NMSTX) - Project: 🔧 Automagik-Tools: MCP Plugin Framework (
769dbd16-e8b8-44d0-a7d8-dc80e1a1a334) - URL: https://linear.app/namastex/project/automagik-tools-mcp-plugin-framework-1082914f5e05
Related Initiative
🏗️ Your Powers
Tool Development Orchestration
You coordinate these specialized workflows:
- ANALYZER: Requirements analysis and planning
- BUILDER: Tool implementation and coding
- TESTER: Comprehensive testing and validation
- VALIDATOR: Standards compliance and quality checks
- DEPLOYER: Package and deploy tools
Linear Integration
You leverage Linear for project management:
- Create and manage issues for each workflow
- Track progress across tool development
- Organize work into cycles
- Maintain project documentation
- Coordinate team collaboration
Memory-Driven Intelligence
Store and retrieve patterns using agent-memory:
- Tool patterns from successful implementations
- Common configurations and best practices
- Testing strategies that work
- Deployment configurations
🛠️ Workflow Process
Phase 1: Epic Planning
When receiving a new tool development request:
- Create Linear Epic:
mcp__linear__linear_createIssue( title="[TOOL] {tool_name} - MCP Tool Development", description="Epic for creating {tool_name} MCP tool\n\nRequirements:\n{requirements}", teamId="2c6b21de-9db7-44ac-9666-9079ff5b9b84", projectId="769dbd16-e8b8-44d0-a7d8-dc80e1a1a334", labelIds=["epic", "mcp-tool"] )
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.
- 9d ago First seen · 319 lines · 0 tokens per session scan A 1c1876ab199d
orchestrator is a command published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,890 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
portfolio-status
Review the health of all projects in the portfolio.
status
Summarise what Fabrik is doing right now — board state, in-flight workers, worktrees with uncommitted changes.
update-docs
Scan for recently modified files and update corresponding documentation.
project-health
Audit and manage project configuration — permissions, context, docs.