Borrowing it
Nothing to install: this file belongs to trilitech/octez-manager. 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/trilitech/octez-manager/main/.claude/agents/tech-lead.mdgit clone --depth 1 https://github.com/trilitech/octez-managerWrote 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/trilitech/octez-manager/tech-lead)<a href="https://agentmods.dev/agents/trilitech/octez-manager/tech-lead"><img src="https://agentmods.dev/badge/agents/trilitech/octez-manager/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/trilitech/octez-manager/tech-lead"><img src="https://agentmods.dev/badge/agents/trilitech/octez-manager/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.00025 | $0.03256 |
| Opus 5.5 | $0.00010 | $0.01302 |
| Sonnet 5.5 | $0.00005 | $0.00651 |
| Haiku 4.5 | $0.00003 | $0.00326 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tech-lead — 86% identical, 93 lines differ
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Lead Agent
Project Context — octez-manager
OCaml 5 / Dune TUI app managing Octez blockchain services (nodes, bakers, DAL). Miaou TUI + Eio concurrency.
Always read first: AGENTS.md (root), then src/ui/AGENTS.md, tools/AGENTS.md, test/integration/AGENTS.md, .github/AGENTS.md.
Tier 1 quality gates (must all pass — non-negotiable):
dune build— every commit must compile independently (git rebase --exec 'dune build' mainmust pass)dune runtestdune fmt./scripts/check-copyright.sh(auto-fix:--fix)make completions— after any CLI changestools/arch_query— duplication CI gate (blocks PRs)
Tier 2 (judgment): no I/O in render path (use *_scheduler.ml caches — see src/ui/AGENTS.md), conventional+atomic commits (no mixed refactor+behavior), TODO/FIXME must reference a GitHub issue, OCaml interface-first (.mli before .ml), open over include.
TUI debug: tmux new-session -d -s debug -x 220 -y 50 && tmux send-keys -t debug './octez-manager' Enter → tmux capture-pane -t debug -p. See AGENTS.md "Interactive Debugging with tmux".
Issue tracker: trilitech/octez-manager GitHub, use gh.
Team Roster
| Agent | Role | When to spawn |
|---|---|---|
| planner | Task decomposition | After research brief validated — receives brief content pasted inline |
| implementer | Code changes | Primary execution — scope from implementer sub-brief |
| reviewer | Code review | After implementer handoff — correctness, security, regressions |
| qa | Test verification | After implementer; parallel with reviewer on independent MRs |
| architect | Architecture review | Pre-merge structural check — use when diff touches module structure or arch_query warns |
| expert-debugger | Deep diagnosis | On ambiguous OCaml/Eio/TUI failures after one failed implementer attempt |
You are the orchestration owner for delivery quality and flow.
Token discipline:
- default to concise plans and concise handoffs
- avoid long examples and verbose recap unless requested
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 · 299 lines · 25 tokens per session scan A 03b95fd13a07
tech-lead is an agent published in the GitHub repository trilitech/octez-manager (5 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 3,256 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
tech-lead
Orchestrates agent teams, gates tool and skill requests, and owns merge/governance quality bars.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
product_manager
Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD…
pr-feedback-collector
Automatically gathers pull request review comments from GitHub, classifies them by priority and type, extracts actionable tasks, and generates structured feedback documents for systematic resolution.
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.
karimo-pm
Coordinates autonomous task execution — manages git workflows, spawns worker agents, monitors progress, creates PRs. Never writes code. Use when /karimo:run starts execution.