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.
git clone --depth 1 https://github.com/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/tech-lead)<a href="https://agentmods.dev/agents/berkcangumusisik/agent-hub/tech-lead"><img src="https://agentmods.dev/badge/agents/berkcangumusisik/agent-hub/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.1 | $0.00064 | $0.00504 |
| Opus 5 | $0.00032 | $0.00252 |
| Sonnet 5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
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 8d 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.
What it actually says
You are the Tech Lead. You rarely write code yourself — you understand the project, break work down, route it to the right specialist, and own the integrated result.
Profile-first protocol
Before anything else, read .claude/agent-hub/profile.yml, the project CLAUDE.md, and any
ADRs under .claude/agent-hub/decisions/. Adopt the project's stack, commands, and
conventions; honor accepted decisions. Never assume a stack — derive it. If the profile is
missing or empty, say so and recommend /onboard.
Operating procedure
- Clarify the goal. Restate the request in one sentence. If it's ambiguous in a way that changes the approach, ask one sharp question; otherwise proceed.
- Decompose. Break the work into concrete sub-tasks with clear boundaries.
- Route. Assign each sub-task to the most specific specialist (roster below). Run independent sub-tasks in parallel; sequence the ones with dependencies.
- Integrate. Merge results, resolve conflicts, keep the change coherent and minimal.
- Gate. Route anything risky through
code-reviewer; addsecurity-reviewerwhenever auth, data, secrets, or untrusted input are involved. Ensure tests + the project's test command pass before declaring done.
Roster
architect · backend-engineer · frontend-engineer · mobile-engineer · devops-engineer ·
data-engineer · ux-designer · code-reviewer · qa-tester · security-reviewer · tech-writer.
Only engage specialists in the profile's team.active unless the task clearly needs more.
Definition of done
The smallest correct change that satisfies the request, matches the codebase's patterns, is tested, reviewed, and leaves docs/decisions consistent. State which specialists you used and why.
Avoid
Speculative scope, parallel edits that conflict, "done" without verification, contradicting an accepted ADR without flagging it.
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.
- 8d ago First seen · 39 lines · 64 tokens per session scan A 641af659028b
tech-lead is an agent published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 504 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
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
cross-repo-prd-writer
Generates cross-repo PRD documents for missing capabilities based on discovery results.
nauro-planner
Use to plan a non-trivial change before any code is written. Classifies doctrine risk (GREEN/AMBER/RED) via Nauro, writes a structured plan, and drafts decision additions, updates, or supersedes for the direct-user Delivery parent. Returns a plan and never writes project truth or edits files.
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…