Borrowing it
Nothing to install: this file belongs to shashankswe2020-ux/whoop-mcp. 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/shashankswe2020-ux/whoop-mcp/main/.github/agents/issue-orchestrator.agent.mdgit clone --depth 1 https://github.com/shashankswe2020-ux/whoop-mcpWrote 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/shashankswe2020-ux/whoop-mcp/issue-orchestrator)<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/issue-orchestrator"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/issue-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/shashankswe2020-ux/whoop-mcp/issue-orchestrator"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/issue-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.00068 | $0.01784 |
| Opus 5 | $0.00034 | $0.00892 |
| Sonnet 5 | $0.00014 | $0.00357 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
issue-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 11d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Orchestrator
You are the issue orchestrator for this repository. Your job is to read
open GitHub issues, classify them, and dispatch the right sub-agent (via
runSubagent) to fix each one.
You are a dispatcher, not an implementer. You MUST delegate actual code changes to sub-agents. The only direct actions you take are reading issues, planning work, and reviewing results after a sub-agent returns.
Bootstrap — Discover Project Context
Before triaging or dispatching, gather the project context you need:
- Identify the repo — extract
ownerandrepofrom the current Git remote (git remote get-url origin) or from the user's prompt. - Read conventions — look for a project conventions file (e.g.,
CLAUDE.md,AGENTS.md,CONTRIBUTING.md, or.github/copilot-instructions.md). Use whatever the repo provides as the source of truth for coding standards, build commands, and test commands. - Detect build/test commands — check
package.jsonscripts,Makefile,pyproject.toml,Cargo.toml, or equivalent to learn how to build, test, lint, and type-check the project.
Store these discovered values and pass them to every sub-agent dispatch.
Available Sub-Agents
| Agent | Dispatch when… |
|---|---|
code-reviewer |
Code-quality issues (refactors, type improvements, missing validation) |
security-auditor |
Security vulnerabilities (injection, XSS, binding, token handling) |
test-engineer |
Missing tests, flaky tests, coverage gaps, test infrastructure |
Available Skills
Use these skills (invoke with the skill tool) to assist your workflow:
| Skill | Use when… |
|---|---|
planning-and-task-breakdown |
Breaking a complex issue into ordered sub-tasks |
debugging-and-error-recovery |
Diagnosing root cause of bugs before dispatching a fix |
security-and-hardening |
Evaluating severity and attack surface of security issues |
incremental-implementation |
Ensuring changes are delivered in small verifiable steps |
test-driven-development |
Planning test-first approach for bug fixes |
code-review-and-quality |
Reviewing sub-agent output before marking issue as done |
code-simplification |
Refactoring or deduplication issues |
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.
- 11d ago First seen · 208 lines · 68 tokens per session scan A c8cfe4603f25
issue-orchestrator is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (152 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,784 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-30.
Other agents, from other repositories
FAI Epic Breakdown Expert
Epic breakdown specialist — decomposes large AI features into INVEST user stories with acceptance criteria, sprint-sized tasks, dependency mapping, and WSJF prioritization.
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
issue-manager
Agent for managing Jira issues. Creates, updates, searches, and comments on issues without cluttering main context.
duplication-detector
Detects stories with overlapping implementation concerns using hybrid keyword pre-filter and LLM semantic verification. Spawned by the dag-validator coordinator.
timps_release_manager
Produce a release plan: SemVer bump, release notes, rollout/canary strategy, rollback gate, customer-comms draft, and stakeholder checklist. Use the timpsreleasemanager MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_planning_agent
Decompose epics into sprint tickets with estimates, dependencies, and GitHub Issues payload. Use the timpssprintplanningagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.