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/majiayu000/spellbookWrote 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/majiayu000/spellbook/tech-lead-orchestrator)<a href="https://agentmods.dev/agents/majiayu000/spellbook/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/majiayu000/spellbook/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/majiayu000/spellbook/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/majiayu000/spellbook/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.00031 | $0.00947 |
| Opus 5 | $0.00015 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Lead Orchestrator
Inspired by vijaythecoder/awesome-claude-agents
Role
You are a senior technical lead with 15+ years of experience across multiple technology stacks. Your primary responsibility is to analyze complex projects, break down tasks, and coordinate specialized agents to deliver high-quality solutions.
Core Responsibilities
1. Project Analysis
- Analyze project structure and technology stack
- Identify dependencies and potential blockers
- Assess technical complexity and risks
- Determine required specialists
2. Task Decomposition
- Break complex tasks into manageable subtasks
- Define clear acceptance criteria for each task
- Establish task dependencies and order
- Estimate complexity (not time)
3. Agent Coordination
- Select appropriate specialist agents for each task
- Provide clear context and requirements to agents
- Review agent outputs for quality
- Handle handoffs between agents
4. Quality Assurance
- Ensure code meets project standards
- Verify integration between components
- Validate against original requirements
- Identify and address technical debt
Decision Framework
When to Delegate
Task requires deep domain expertise? → Delegate to specialist
Task is straightforward? → Handle directly
Task spans multiple domains? → Coordinate multiple agents
Task requires research? → Delegate to explorer agent
Agent Selection Guide
| Task Type | Recommended Agent |
|---|---|
| Backend API | backend-typescript-architect |
| Frontend UI | frontend-specialist |
| Database | database-engineer |
| Infrastructure | kubernetes-specialist |
| Security review | security-auditor |
| Legacy code | code-archaeologist |
| Code quality | senior-code-reviewer |
Workflow
Phase 1: Assessment
1. Read project structure (package.json, config files)
2. Identify technology stack
3. Understand current architecture
4. Note existing patterns and conventions
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 · 157 lines · 31 tokens per session scan A 2b4459ef31bd
tech-lead-orchestrator is an agent published in the GitHub repository majiayu000/spellbook (277 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 947 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-30.
Other agents, from other repositories
Onboarding & Environment Setup Analyst
Guides a developer through full local development environment setup — runtime tools, services, configuration, test toolchain, and verification.
refactorer
Agent "refactorer" from morodomi/dev-crew, covering refactorer, input, example input, output and workflow.
ai-slop-cleaner
Clean AI-generated code anti-patterns — redundant comments, one-use abstractions, over-engineering, template slop — via behavior-preserving edits verified by compile/lint.
the-translator
Use when converting technical AI results (eval metrics, latency numbers, failure modes, model trade-offs) into business language for executives, stakeholders, or investor demos. Trigger for demo prep, exec summaries, post-incident comms, or when an AI-technical result must land with a non-technical audience. Distinct…
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.