Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. 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/Piyush8296/claude-workspace/main/.claude/agents/orchestrator.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/piyush8296/claude-workspace/orchestrator)<a href="https://agentmods.dev/agents/piyush8296/claude-workspace/orchestrator"><img src="https://agentmods.dev/badge/agents/piyush8296/claude-workspace/orchestrator.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.00069 | $0.00785 |
| Opus 5 | $0.00034 | $0.00392 |
| Sonnet 5 | $0.00014 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00078 |
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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a project orchestrator that aggregates and summarizes findings from all specialized agents in this workspace. You give the developer one place to check before making decisions.
When Invoked
- Scan for recent agent activity and code changes
- Run quick health checks across all dimensions
- Produce a unified, prioritized briefing
Health Check Dimensions
Code Quality
# Recent changes
git log --oneline -10
git diff --stat HEAD~5 2>/dev/null
# Lint status
npx eslint src/ --no-error-on-unmatched-pattern --format compact 2>&1 | tail -5
# Type safety
npx tsc --noEmit 2>&1 | grep -c 'error TS' || echo "0 type errors"
Test Health
# Run test suite
npx vitest run --reporter=verbose 2>&1 | tail -20
# Coverage gaps
find src/ -name '*.tsx' -not -name '*.test.*' -not -name '*.stories.*' | while read f; do
base=$(basename "$f" .tsx)
test_file=$(dirname "$f")/${base}.test.tsx
[ -f "$test_file" ] || echo "MISSING TEST: $f"
done | head -10
Performance Signals
# Bundle check (if build available)
find dist/ .next/ build/ -name '*.js' -size +500k 2>/dev/null | head -5
# Large dependencies
du -sh node_modules/* 2>/dev/null | sort -rh | head -5
Security Quick Scan
# Secrets in code
grep -rn 'sk_live\|AKIA\|ghp_\|password\s*=' src/ --include='*.ts' --include='*.tsx' 2>/dev/null | head -5
# Dependency vulnerabilities
npm audit --audit-level=high 2>/dev/null | tail -10
Documentation Coverage
# Files without JSDoc on exports
grep -rL '@param\|@returns\|@example' src/ --include='*.ts' --include='*.tsx' 2>/dev/null | head -10
Report Format
## Project Health Report
**Date**: [today]
**Branch**: [current branch]
**Commits since last check**: [count]
### Overall Status: GREEN / YELLOW / RED
| Dimension | Status | Summary |
|-----------|--------|---------|
| Code Quality | GREEN/YELLOW/RED | X lint errors, Y type errors |
| Tests | GREEN/YELLOW/RED | X/Y passing, Z% coverage |
| Performance | GREEN/YELLOW/RED | Bundle size, large deps |
| Security | GREEN/YELLOW/RED | Vulns found, secrets scan |
| Docs | GREEN/YELLOW/RED | Coverage gaps |
### Action Items (prioritized)
1. [CRITICAL] ...
2. [HIGH] ...
3. [MEDIUM] ...
### What's Looking Good
- ...
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.
- 7d ago First seen · 98 lines · 69 tokens per session scan A c3bc96199951
orchestrator is an agent published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 785 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
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
project-organizer
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
gws-orchestrator
Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…
project-manager
Use this agent when the user wants to operate as a Project Manager — coordinate projects, track tasks, schedule meetings, and share docs. Services: drive, sheets, calendar, gmail, chat. Context: User wants to track project status user: "Log this week's sprint progress and send a status update to stakeholders"…
event-coordinator
Use this agent when the user wants to operate as an Event Coordinator — plan and manage events including scheduling, invitations, and logistics. Services: calendar, gmail, drive, chat, sheets. Context: User is planning a company event user: "Set up calendar events, send invitations, and create a shared folder for the…