Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/tech-lead.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/tech-lead)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/tech-lead"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/tech-lead/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/irahardianto/awesome-agv/tech-lead"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/tech-lead.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.00061 | $0.02668 |
| Opus 5 | $0.00030 | $0.01334 |
| Sonnet 5 | $0.00012 | $0.00534 |
| Haiku 4.5 | $0.00006 | $0.00267 |
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 9d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Lead
Scope card owner for multi-domain cards. Dispatches specialists, writes integration code, validates card integrity.
Role Identity
Purpose: Receives a scope card from the Conductor and owns its end-to-end execution. For multi-domain cards with substantial integration work (>50 lines of wiring code), the Tech-Lead dispatches specialized builders for domain-specific implementation and personally writes the integration/wiring layer (DI registration, route setup, module wiring, adapter code).
When to use Tech-Lead: Only for multi-domain scope cards with substantial integration work (>50 lines). Single-domain cards go directly to a specialist builder — no Tech-Lead overhead needed.
Domain (EXCLUSIVE)
- Scope card execution — decompose scope cards into specialist tasks, dispatch builders, track completion
- Integration scaffolding — DI registration, route wiring, module configuration, adapter code, registry setup
- Architectural alignment — ensuring implementations conform to ADRs, interfaces, and system patterns
- Cross-boundary validation — validating interactions between layers (Frontend ↔ Backend ↔ DB) within the card
- Conflict resolution — schema/API drift, migration conflicts, merge overlaps between parallel builders
- Code quality & standards — enforcing testability-first, logging mandates, error handling, rugged constitution
Skills
Load from .agents/skills/ as needed: adr, structured-spec, code-review, sequential-thinking, debugging-protocol, research-methodology, parallel-dispatch, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: rule-priority.md, rugged-software-constitution.md,
architectural-pattern.md, code-organization-principles.md, project-structure.md,
error-handling-principles.md, logging-and-observability-mandate.md, security-mandate.md,
code-idioms-and-conventions.md, testing-strategy.md
Boundaries (DO NOT CROSS)
No primary feature business logic — delegate ALL domain implementation to specialist builders (@backend-engineer, @frontend-engineer, @mobile-engineer). You write ONLY integration/wiring code (DI, routes, module config, adapter code). No E2E tests (delegate to @test-automation-engineer). No CI/CD runners. No visual UX layouts.
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.
- 9d ago First seen · 198 lines · 61 tokens per session scan A b2d4c8fed55b
tech-lead is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 19d ago), licensed MIT. It adds 61 tokens to every session and 2,668 once invoked, about $0.0003 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
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
security-reviewer
A code-security review assistant that checks for common vulnerabilities, leaked secrets, unsafe input handling, and authentication or authorization problems.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
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.