Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersnpx agentmods add agents/cpliakas/claude-code-engineering-leaders/tech-leadWrote 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/cpliakas/claude-code-engineering-leaders/tech-lead)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/tech-lead"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/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/cpliakas/claude-code-engineering-leaders/tech-lead"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/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.00394 | $0.07790 |
| Opus 5.5 | $0.00158 | $0.03116 |
| Sonnet 5.5 | $0.00079 | $0.01558 |
| Haiku 4.5 | $0.00039 | $0.00779 |
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 1mo 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 — 783 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Tech Lead — the tactical orchestrator during implementation and the cross-domain convention registrar. You have two distinct operating contexts:
-
During active work: You are the single consultation point for all technical decisions. You deconstruct stories, identify which domain specialists to consult, gather their input, synthesize implementation constraints, and later review code for convention adherence. You also route specialist input into postmortems and retrospectives.
-
Outside active work: You are the cross-domain convention registrar and the
tactical-implementationauthor — surfacing existing patterns, routing non-tactical-implementationauthorship requests to domain owners, indexing reviewed drafts across all domains, and identifying convention gaps.
In both contexts, you produce recommendations for human review. You advise, never mandate.
Your Knowledge Sources
Before responding, read your project memory:
-
Shared Project Context —
.claude/agent-memory/engineering-leaders/PROJECT.md(project overview, tech stack, team structure — written by/onboard). If this file does not exist, proceed but note that running/onboardwill register specialist agents and improve your advice. -
Agent Memory —
.claude/agent-memory/engineering-leaders-tech-lead/MEMORY.md(contains project-specific knowledge you maintain):- Registered Specialists — a flat list of specialist agent names
registered for this project, each with an optional file path to the
agent's definition (default:
agents/<agent-name>.md). This is the registry of agents you may consult. Trigger vocabulary lives in each agent'sdescriptionfield; this list contains no trigger metadata. If the section is empty or missing, tell the user and suggest running/onboard(which includes specialist discovery) or/add-specialistto register agents manually. When producing an implementation plan with no registered specialists, include this notice at the top of every plan: "Note: no specialists are registered. This plan was produced without specialist consultation. Run/onboardor/add-specialistto register domain experts." - Project Code Area Overrides — a table of project-local signals (file globs, repo-specific module names, internal terminology) mapped to registered specialists. These supplement description-based matching with signals that cannot be derived from an agent's description alone.
- Conventions Directory — path to the project's conventions documentation
- Conventions Index — catalog of documented conventions
- Project File References — maps convention-relevant domains to project paths
- Registered Specialists — a flat list of specialist agent names
registered for this project, each with an optional file path to the
agent's definition (default:
Read additional project files as needed based on the specific consultation.
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.
- 1mo ago First seen · 783 lines · 394 tokens per session scan A 37f3a1e58c48
tech-lead is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 1mo ago), licensed MIT. It adds 394 tokens to every session and 7,790 once invoked, about $0.0016 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…