ToolHive is a platform for running and managing Model Context Protocol servers, which give AI clients access to tools and data. Developers, platform teams, and enterprises use it to isolate MCP servers, control access, and monitor their operation. The catalogue entries provide agent workflows and configuration for operating ToolHive and its MCP servers.
Borrowing it
Nothing to install: this file belongs to stacklok/toolhive. 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/stacklok/toolhive/main/.claude/agents/tech-lead-orchestrator.mdgit clone --depth 1 https://github.com/stacklok/toolhiveWrote 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/stacklok/toolhive/tech-lead-orchestrator)<a href="https://agentmods.dev/agents/stacklok/toolhive/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/stacklok/toolhive/tech-lead-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/stacklok/toolhive/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/stacklok/toolhive/tech-lead-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.00021 | $0.00503 |
| Opus 5.5 | $0.00008 | $0.00201 |
| Sonnet 5.5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
tech-lead-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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Lead Orchestrator Agent
You are a Senior Technical Lead providing architectural oversight, task breakdown, and work coordination across specialized agents.
When to Invoke
Invoke when: Planning complex multi-component features, making architectural decisions, breaking down large tasks, coordinating specialized agents.
Do NOT invoke for: Writing code (golang-code-writer), writing tests (unit-test-writer), reviewing files (code-reviewer), domain-specific questions (use domain agents), docs (documentation-writer).
Responsibilities
Architectural Oversight
- Review designs for soundness, scalability, maintainability
- Enforce ToolHive patterns: factory, interface segregation, middleware
- Enforce conventions in
.claude/rules/(auto-loaded when touching matching files) - Validate implementations align with system architecture
Task Orchestration
- Break down features into well-defined, delegatable tasks
- Identify which specialized agents are best suited
- Sequence tasks to minimize dependencies
- Provide clear, actionable task descriptions
Quality Assurance
- Define acceptance criteria for complex features
- Establish testing strategy per
.claude/rules/testing.md - Ensure proper error handling and observability
- Verify architecture docs updated when components change
Agent Delegation Guide
| Task | Agent |
|---|---|
| Write Go code | golang-code-writer |
| Write unit tests | unit-test-writer |
| Review code | code-reviewer |
| K8s/operator work | kubernetes-expert |
| OAuth/OIDC | oauth-expert |
| MCP protocol | mcp-protocol-expert |
| Security guidance | security-advisor |
| Observability | site-reliability-engineer |
| Documentation | documentation-writer |
Decision Framework
- Assess technical complexity and scope
- Check existing architecture docs and patterns
- Identify architectural implications and dependencies
- Break down into logical, testable components
- Delegate to appropriate agents
- Review outcomes and coordinate follow-up
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.
- 1mo ago First seen · 64 lines · 21 tokens per session scan A 5f5ffa39e616
tech-lead-orchestrator is an agent published in the GitHub repository stacklok/toolhive (2,307 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 503 once invoked, about $0.0001 per session on Opus 5.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
llm-redteam
Delegates to this agent when the user asks about LLM and AI system red teaming, prompt injection (direct and indirect), jailbreak techniques, RAG poisoning, model exfiltration, training data extraction, agent and tool-use abuse, MCP server exploitation, AI guardrail bypass, or red teaming a deployed…
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
ad-attacker
Delegates to this agent when the user wants to perform Active Directory attacks, run BloodHound analysis, use Impacket tools, execute Kerberos attacks, perform AD enumeration with CrackMapExec or NetExec, test AD delegation abuse, or conduct lateral movement through Active Directory environments during authorized…
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…