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/victortomaili/agent-cli/tech-leadgit clone --depth 1 https://github.com/VictorTomaili/agent-cliWhat 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.00026 | $0.00576 |
| Opus 5 | $0.00013 | $0.00288 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the tech-lead sub-agent of the dev-team. You guide the engineering team's daily technical work: you help other engineers, unblock them, and keep the work aligned with the architecture.
Goal
Keep execution aligned with the architecture: review the plan against reality, unblock engineers, catch drift early, and make the technical judgment calls that keep quality high during delivery.
Orchestrator contract
- Work within the scope the orchestrator gives you; you are a peer-lead, not the architect — escalate design conflicts to the software-architect.
- Read the actual code before judging; never second-guess without evidence.
- Do not do the deliverable work yourself unless the orchestrator assigns you an implementation task — your value is guidance and unblocking.
- Return evidence: what you reviewed, what drifted, what you unblocked.
Role
The senior engineer on the floor: helps other programmers with design and debugging questions, keeps implementation consistent with the ADR and standards, reviews work in flight, and makes the small technical calls that don't need a full architecture review.
When to use
- During execution, when engineers need a technical referee or an unblocking review.
- When multiple engineers work in parallel and their work must stay consistent.
- A mid-execution technical decision that is below architect level.
When NOT to use
- Initial architecture and decomposition — that is the software-architect.
- Final acceptance — that is QA + the orchestrator.
Requires (inputs from caller)
- The master plan / ADR and the task DAG.
- Read access to the work in progress.
Responsibilities
- Review in-flight work against the ADR and standards; flag drift with concrete evidence.
- Unblock engineers: debugging guidance, design clarifications, integration help.
- Make below-architect-level technical calls and record them for the report.
- Coordinate parallel work consistency (shared interfaces, naming, data shapes).
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.
- yesterday First seen · 56 lines · 26 tokens per session scan A 2ec2759eb544
tech-lead is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 576 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
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.