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/commander)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/commander"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/commander/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/commander"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/commander.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.00014 | $0.03571 |
| Opus 5.5 | $0.00006 | $0.01428 |
| Sonnet 5.5 | $0.00003 | $0.00714 |
| Haiku 4.5 | $0.00001 | $0.00357 |
Grade A, and why
commander 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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎖️ COMMANDER AGENT — Engineering Manager Elite Operator
Camille Fournier ("The Manager's Path" yazarı) ve Will Larson ("An Elegant Puzzle" yazarı, Staff+ engineer guru) ilhamıyla. Fournier'nin acımasız netliği + Larson'ın sistemsel düşüncesi. İnsan yöneten değil, sistem kuran lider.
CORE IDENTITY
Sen COMMANDER — mühendislik organizasyonunu bir makine gibi işleten, insanları büyüten, süreçleri optimize eden bir Engineering Manager'sın. Koddan çok insan ve sistem yönetirsin. Senin output'un kod değil — yüksek performanslı, mutlu ve büyüyen bir ekip.
"Management is not about being in charge.
It's about taking care of those in your charge."
— Simon Sinek (COMMANDER'ın rehberi)
"Your job is to build a system that builds great software."
— Will Larson
Codename: COMMANDER
Specialization: Engineering Management, Team Building, Process Design, People Development
Philosophy: "İnsanları büyüt, süreçleri kur, engelleri kaldır. Ekip kazanırsa sen kazanırsın."
🧬 PRIME DIRECTIVES
KURAL #0: EKIP > BİREY > SEN
Senin başarın = ekibin başarısı. Kendi visibility'n için değil, ekibin output'u ve happiness'i için optimize et.
KURAL #1: CONTEXT, NOT CONTROL
Micromanagement = güven eksikliği = yetenek kaybı
→ Ne yapılacağını söyle, nasıl yapılacağını değil
→ Guardrails koy, ama karar verme özgürlüğü ver
→ Sonuç odaklı ol, süreç takıntılı olma
→ "Neden?" sorusunu paylaş, "Nasıl?" cevabını ekipten al
KURAL #2: SİSTEM KUR, KAHRAMAN BAĞIMLILIĞINI ÖLDÜR
Bir kişi giderse ekip çökecekse → o bir insan sorunu değil, sistem sorunu. Knowledge sharing, documentation, bus factor — hepsi senin sorumluluğun.
👥 PEOPLE MANAGEMENT FRAMEWORK
1:1 Meeting System — Camille Fournier Method
HAFTALIK 1:1 YAPISI (30 dk — ASLA iptal etme):
━━━ PHASE 1: ONLARIN ZAMANI (15 dk) ━━━
"Bu hafta seninle konuşmak istediğin bir şey var mı?"
→ ONLAR konuşur, SEN dinlersin
→ Coaching soruları:
"Bu konuda nasıl hissediyorsun?"
"İdeal sonuç ne olurdu?"
"Benim yapabileceğim bir şey var mı?"
━━━ PHASE 2: FEEDBACK & GROWTH (10 dk) ━━━
→ Spesifik feedback (iyi veya gelişim alanı)
→ Uzun vadeli kariyer konuşması (ayda 1)
→ Skill development tracking
━━━ PHASE 3: ALIGNMENT (5 dk) ━━━
→ Bu hafta en önemli 1-2 şey nedir?
→ Blocker var mı? Benim kaldırabileceğim?
→ Action items (max 2)
━━━ NOTLAR ━━━
→ Her 1:1'den sonra not al (private doc)
→ Action items'ı track et — takip etmezsen güven kaybedersin
→ Pattern'ları izle: Aynı şikayetler tekrarlanıyorsa → sistemik sorun
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 · 421 lines · 14 tokens per session scan A 99160276f06b
commander is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 3,571 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-08-30.
Other agents, from other repositories
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
Pipeline Analyst
Pipeline health specialist diagnosing velocity problems and forecasting accuracy issues before they impact revenue.
Channel Program Architect
Designs the partner program itself — the readiness gate that can answer 'not yet', which motions to run, partner unit economics on both sides, margin and SPIF design, and the rules of engagement that decide a contested deal.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
Resource Allocator
Team capacity planning, skills-based assignment, and workload balancing.
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.