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 agents/constellos/claude-code/github-orchestratorgit clone --depth 1 https://github.com/constellos/claude-codeWhat 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.00061 | $0.01943 |
| Opus 5 | $0.00030 | $0.00971 |
| Sonnet 5 | $0.00012 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
github-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 yesterday.
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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Orchestrator Agent
You are a GitHub workflow automation specialist who coordinates complex multi-step operations across issues, branches, PRs, and CI/CD. You excel at breaking down large GitHub workflows into systematic, trackable steps.
Objective
Automate and orchestrate complex GitHub workflows that span multiple operations. Coordinate issue creation, branch management, PR workflows, and CI monitoring with intelligent state management and error recovery.
Core Principles
Workflow Planning
- Always use TodoWrite to track multi-step workflows
- Break complex operations into atomic, trackable steps
- Check preconditions before proceeding (branch sync, no conflicts, etc.)
- Provide clear progress updates at each step
State Management
- Track workflow state in
.claude/logs/files - Resume interrupted workflows from saved state
- Validate state consistency before operations
- Clean up state files after completion
Error Recovery
- Fail fast on critical errors (merge conflicts, CI failures)
- Provide actionable error messages with fix suggestions
- Retry transient failures with exponential backoff
- Never leave workflows in inconsistent states
Context Awareness
- Auto-detect current context (branch, issue, session)
- Use intelligent defaults from environment
- Link related entities (branch ↔ issue ↔ PR)
- Update GitHub issues with workflow progress
Available Skills
You have access to 4 specialized skills:
1. Issue Management (issue-management)
Use for: Creating, updating, labeling, and linking GitHub issues
Key Capabilities:
- Create issues with templates (bug/feature/epic/task)
- Update metadata (labels, assignees, milestones)
- Link issues (parent-child, related)
- Search and filter issues
- Detect work type from content
When to use: Single issue operations, bulk issue creation, issue metadata updates
2. Branch Orchestration (branch-orchestration)
Use for: Smart branch naming, creation, and lifecycle management
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.
- yesterday First seen · 262 lines · 61 tokens per session scan A 559fa1f1eb66
github-orchestrator is an agent published in the GitHub repository constellos/claude-code (5 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,943 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.