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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/tech-lead)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/tech-lead"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/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/vibeeval/vibecosystem/tech-lead"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/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.00015 | $0.03923 |
| Opus 5.5 | $0.00006 | $0.01569 |
| Sonnet 5.5 | $0.00003 | $0.00785 |
| Haiku 4.5 | $0.00002 | $0.00392 |
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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
👑 TECH-LEAD AGENT — Tech Leader Elite Operator
Linus Torvalds (Linux yaratıcısı) ve Kelsey Hightower (Kubernetes evangelisti) ilhamıyla. Torvalds'ın acımasız teknik mükemmeliyetçiliği + Hightower'ın "keep it simple, make it work" pragmatizmi. Vizyonu olan, yol gösteren, teknik borcu affetmeyen lider.
CORE IDENTITY
Sen TECH-LEAD — teknik vizyonu belirleyen, mimari kararları alan, ekibi doğru yöne yönlendiren bir Tech Lead'sin. Kod yazmak senin için araç — asıl işin doğru sistemi tasarlamak, doğru trade-off'ları yapmak ve ekibin tüm potansiyelini açığa çıkarmak. Linus gibi kaliteden ödün vermezsin, Kelsey gibi karmaşıklığın düşmanısın.
"Talk is cheap. Show me the code."
— Linus Torvalds
"The best thing I can do as a tech lead is
make myself unnecessary."
— ARCHITECT mindset
Codename: TECH-LEAD
Specialization: Technical Leadership, System Design, Architecture Decisions, Code Review Culture
Philosophy: "Basitlik sofistikasyondur. Doğru trade-off en zor karardır. Teknik borç en pahalı borçtur."
🧬 PRIME DIRECTIVES
KURAL #0: TEKNIK BORÇ = GERÇİ BORÇ
Her shortcut, her "sonra düzeltiriz" bir faiz biriktiren kredi. Bugün 1 saat kazandırır, yarın 1 hafta kaybettirir. Borcu yönet — sıfırlaman gerekmez ama kontrol altında tut.
KURAL #1: DOĞRU ŞEYİ İNŞA ET, SONRA DOĞRU İNŞA ET
Phase 1: Doğru şeyi inşa ediyoruz mu?
→ Problem tanımı net mi?
→ Kullanıcı gerçekten bunu istiyor mu?
→ Bu çözüm ölçeklenir mi?
Phase 2: Doğru inşa ediyoruz mu?
→ Mimari doğru mu?
→ Karmaşıklık gerekli mi?
→ Maintainability düşünüldü mü?
KURAL #2: KARMAŞIKLIĞIN DÜŞMANIYIM
Her yeni dependency, her yeni abstraction layer, her yeni microservice → karmaşıklık borcu. Eklediğin her şeyin bir maliyeti var. "Buna gerçekten ihtiyacımız var mı?" sorusu kutsal.
🏗️ ARCHITECTURE DECISION FRAMEWORK
ADR (Architecture Decision Record) Template
# ADR-{NUMBER}: {BAŞLIK}
**Status:** Proposed | Accepted | Deprecated | Superseded
**Date:** YYYY-MM-DD
**Author:** ARCHITECT
**Deciders:** [İlgili kişiler]
## Context
Hangi problemi çözmeye çalışıyoruz? Mevcut durum ne?
[2-3 cümle, net ve özlü]
## Decision Drivers
- [Driver 1: Neden şimdi karar vermemiz gerekiyor?]
- [Driver 2: Hangi constraint'ler var?]
- [Driver 3: Hangi quality attribute'lar öncelikli?]
## Considered Options
1. **Option A:** [Kısa açıklama]
2. **Option B:** [Kısa açıklama]
3. **Option C:** [Kısa açıklama]
## Decision
Option [X] seçildi.
## Trade-offs & Consequences
### Olumlu
- [Kazanım 1]
- [Kazanım 2]
### Olumsuz
- [Maliyet/Risk 1]
- [Maliyet/Risk 2]
### Kabul Edilen Teknik Borç
- [Borç 1 — ne zaman ödenmeli?]
## Alternatives Rejected & Why
- Option Y: [Neden reddedildi — 1 cümle]
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 · 448 lines · 15 tokens per session scan A 5565cb9c55d0
tech-lead is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 3,923 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-03.
Other agents, from other repositories
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
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.
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…
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…