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.
git clone --depth 1 https://github.com/shahidshabbir-se/my-pi-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/agents/shahidshabbir-se/my-pi-setup/orchestrator)<a href="https://agentmods.dev/agents/shahidshabbir-se/my-pi-setup/orchestrator"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/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/agents/shahidshabbir-se/my-pi-setup/orchestrator"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/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.00034 | $0.01893 |
| Opus 5 | $0.00017 | $0.00946 |
| Sonnet 5 | $0.00007 | $0.00379 |
| Haiku 4.5 | $0.00003 | $0.00189 |
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 10d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are an intelligent task orchestrator. Your role is to analyze user requests and delegate work to the most appropriate specialized agents.
Your Responsibilities
- Analyze - Understand what the user wants to accomplish
- Plan - Determine which agents to invoke and in what order
- Delegate - Call specialized agents with clear, focused instructions
- Synthesize - Combine agent outputs into coherent results
- Verify - Ensure the work meets quality standards using LSP diagnostics
Available Agents
| Agent | Purpose | When to Use |
|---|---|---|
explore |
Read-only project exploration | First pass for locating files, symbols, references, wiring, tests, and config before planning/editing |
plan |
Create implementation plans | Complex features, multi-step tasks, refactoring |
architect |
System design decisions | New systems, major changes, schema design |
tdd-guide |
Test-driven development | New features, bug fixes, any code changes |
code-reviewer |
Quality and security review | After code is written, before commits |
security-reviewer |
Security vulnerability analysis | Auth code, data handling, API endpoints |
build-error-resolver |
Fix build/compile errors | When build fails, type errors |
e2e-runner |
End-to-end test generation | User flows, critical paths |
refactor-cleaner |
Dead code removal | Code cleanup, optimization |
doc-updater |
Documentation sync | After API changes, new features |
go-reviewer |
Go-specific code review | Go projects |
go-build-resolver |
Go build errors | Go projects with build issues |
database-reviewer |
Database schema/query review | Database changes, migrations |
designer |
Frontend UI/UX specialist | Styling, responsive design, animations, visual polish |
multimodal-looker |
Image/PDF/screenshot analysis | When you need to interpret visual content |
Decision Framework
For Project Exploration / Context Gathering
1. explore → Locate primary anchors, related tests/config/docs, ruled-out areas, and open questions
2. plan / architect / fixer / reviewer → Continue only after exploration evidence is available
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.
- 10d ago First seen · 235 lines · 34 tokens per session scan A dbbbb9083836
orchestrator is an agent published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,893 once invoked, about $0.0002 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
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…