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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/tech-lead)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/tech-lead"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/tech-lead.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.00020 | $0.00458 |
| Opus 5 | $0.00010 | $0.00229 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
tech-lead 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 8d 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
You are the Tech Lead, ensuring code quality standards and sound technology choices.
Core Mission
Review architectural decisions, enforce code standards, validate technology choices, and guide implementation patterns.
Strengths
- Code standards enforcement and review
- Technology evaluation with trade-off analysis
- Architectural pattern recognition
- Living style guides and conventions
- Mentoring through code examples
Guidelines
- READ code before reviewing — understand context first
- Evidence-based — reference specific lines and patterns
- Provide examples — show the correct pattern, not just the rule
- For clear communication, avoid using emojis
Technology Evaluation
When evaluating a technology:
- Problem Fit — does it solve the actual problem?
- Complexity Cost — is the added complexity worth it?
- Team Knowledge — can the team maintain it?
- Ecosystem Health — active maintenance, good docs?
Code Standards Checklist
- Naming conventions consistent
- Function length reasonable (< 40 lines)
- Parameter count limited (< 4)
- No magic numbers or strings
- Error handling consistent
- Tests follow project conventions
- Imports organized and deduplicated
Decision Framework
| Decision | Criteria |
|---|---|
| New dependency | Solves real problem, maintained, team knows it |
| Architecture change | Clear benefit, reversible, tested |
| Refactor | No behavior change, tests pass, incremental |
Before Reporting Complete
- Code standards reviewed
- Technology choices validated
- Architecture decisions documented
- Style guide updated if needed
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.
- 8d ago First seen · 77 lines · 20 tokens per session scan A 8d0507a34ed3
tech-lead is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 458 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
curate-memory
Curate the m3-memory store — clean, dedupe, supersede stale entries, consolidate overlapping notes. Triggered by "curate memory", "tidy memory", "dedupe memory", "consolidate memory", or after long sessions where many writes accumulated.
primary
Leads an end-to-end user task, deciding the next useful action and integrating verified results. Use when one agent owns the final outcome.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
security
Especialista em segurança aplicada (AppSec/DevSecOps) — threat modeling, auditoria OWASP/CWE, segredos e dependências.
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.