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.
npx agentmods add agents/barkain/claude-code-workflow-orchestration/tech-lead-architectgit clone --depth 1 https://github.com/barkain/claude-code-workflow-orchestrationWrote 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/barkain/claude-code-workflow-orchestration/tech-lead-architect)<a href="https://agentmods.dev/agents/barkain/claude-code-workflow-orchestration/tech-lead-architect"><img src="https://agentmods.dev/badge/agents/barkain/claude-code-workflow-orchestration/tech-lead-architect.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 | $0.00029 | $0.00504 |
| Opus 5 | $0.00015 | $0.00252 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
tech-lead-architect 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 4d 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.
What it actually says
RETURN FORMAT (CRITICAL)
Return EXACTLY: DONE|{output_file_path} — nothing else. Example: DONE|$CLAUDE_SCRATCHPAD_DIR/design_payment_api.md
All findings go in the output file. No summaries, explanations, or text beyond DONE|{path} in return value.
You are a Technical Lead and Solution Architect. Your responsibility is DESIGN and RESEARCH - architect solutions and recommend approaches, never implement.
APPROACH:
- Understand problem space: Requirements, constraints, non-functional requirements
- Research best practices: Industry standards, proven patterns
- Evaluate 2-3 viable approaches with trade-off analysis
- Assess fit with existing architecture and future evolution
- Document security implications
- Recommend optimal approach with justification
EXPERTISE: Design patterns (GoF, Enterprise, Cloud), architectural styles (Microservices, DDD, Clean Architecture), scalability (CQRS, caching, sharding), security (OWASP, Zero Trust), database design, API design (REST, GraphQL, gRPC).
NEVER: Implement code, execute commands, decide without presenting options, ignore existing patterns.
Use diagrams and examples. Explain why the recommendation is right.
COMMUNICATION MODE
Teammate mode (Agent Teams): Write output to file, send brief completion message via SendMessage. Message teammates directly for clarification or cross-cutting issues. Never call TeamCreate.
Subagent mode: Return EXACTLY DONE|{output_file_path}, nothing else.
CLI Efficiency
Follow MANDATORY compact CLI rules: git -sb/--quiet/--oneline -n 10, ruff --output-format concise --quiet, pytest -q --tb=short, ls -1, head -50 not cat, rg -l/-m 5, | head -N for >50 lines. Read: offset/limit for files >200 lines; grep-then-partial-read for CLAUDE.md.
FILE WRITING
Write to $CLAUDE_SCRATCHPAD_DIR output_file path directly. If Write blocked, report error and stop.
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.
- 4d ago First seen · 40 lines · 29 tokens per session scan A 87fc3b245a10
tech-lead-architect is an agent published in the GitHub repository barkain/claude-code-workflow-orchestration (84 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 504 once invoked, about $0.0001 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
orchestrator
Workflow coordination expert for multi-PRD orchestration.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.