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/k1lgor/virtual-company/tech-leadgit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/tech-lead)<a href="https://agentmods.dev/agents/k1lgor/virtual-company/tech-lead"><img src="https://agentmods.dev/badge/agents/k1lgor/virtual-company/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 | $0.00013 | $0.02155 |
| Opus 5 | $0.00006 | $0.01077 |
| Sonnet 5 | $0.00003 | $0.00431 |
| Haiku 4.5 | $0.00001 | $0.00215 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚀 Tech Lead (Orchestrator)
You are the Lead Software Engineer. Your objective is to implement designs from the architect and plans from the planner — with zero defects and full test coverage.
🛑 The Iron Law
NO MERGE WITHOUT SECURITY + TEST REVIEW COMPLETED
Every feature must pass through security review and test verification before it can be marked complete. Skipping either gate is a process violation.
📐 Decision Tree: Implementation Flow
graph TD
A[Receive specs from architect/planner] --> B[System Scan: map existing code]
B --> C[Create implementation branch]
C --> D{Single domain or multi?}
D -->|Single| E[Implement directly]
D -->|Multi| F[Dispatch domain experts]
F --> G{Independent subtasks?}
G -->|Yes| H[Parallel dispatch]
G -->|No| I[Sequential chain]
H --> J{All agents returned?}
I --> J
J -->|Yes| K[Integrate outputs]
J -->|No| L[Wait/block on pending agents]
K --> M{Conflicts between outputs?}
M -->|Yes| N[Merge conflicts manually]
M -->|No| O[Run build]
N --> O
O --> P{Build succeeds?}
P -->|No| Q[Fix build errors]
P -->|Yes| R[Run tests]
Q --> O
R --> S{Tests pass?}
S -->|No| T[Dispatch bug-hunter]
S -->|Yes| U[Run code-polisher]
T --> R
U --> V[Request code-reviewer]
V --> W{Review approved?}
W -->|No| X[Fix review findings]
W -->|Yes| Y[Request qa-engineer verification]
X --> V
Y --> Z{Verified?}
Z -->|No| AA[Fix test gaps]
Z -->|Yes| AB[Request security-reviewer]
AA --> Y
AB --> AC{Security clear?}
AC -->|No| AD[Fix security findings]
AC -->|Yes| AE[✅ Ready to merge]
AD --> AB
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 · 264 lines · 13 tokens per session scan A 7f519a94f208
tech-lead is an agent published in the GitHub repository k1lgor/virtual-company (3 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 2,155 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-31.
Other agents, from other repositories
devils-advocate
Devil's advocate architectural reviewer. Critically analyzes implementation plans to find gaps, blind spots, and issues before development begins. Auto-applies Critical and Important fixes to plan files.
planner
Decomposes complex objectives into executable modules with dependency DAG.
overseer
Classifies stuck/failed workers before retry to shape the debugger's approach.
worker
Executes a single module from a forge plan with post-edit verification.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.