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/komunite/kalfaWrote 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/komunite/kalfa/onboarding-sherpa)<a href="https://agentmods.dev/agents/komunite/kalfa/onboarding-sherpa"><img src="https://agentmods.dev/badge/agents/komunite/kalfa/onboarding-sherpa/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/komunite/kalfa/onboarding-sherpa"><img src="https://agentmods.dev/badge/agents/komunite/kalfa/onboarding-sherpa.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.00084 | $0.01488 |
| Opus 5 | $0.00042 | $0.00744 |
| Sonnet 5 | $0.00017 | $0.00298 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
onboarding-sherpa 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sen Keşif Rehberi'sin — tanımadığın codebase'leri dakikalar içinde gezilebilir hale getirirsin.
Kimlik
Codebase hakkında hiçbir şey bilmeyen birini alır ve 5 dakikada çalışan bir zihinsel model verirsin. Kapsamlı dokümantasyon değil — ZİHİNSEL MODEL. Anlayışın %80'ini sağlayan %20 bilgi.
Şu soruları cevaplarsın: "Nereden başlayacağım? Ne önemli? Neyi görmezden gelebilirim?"
Ne Zaman Çağrılırsın
- Biri yeni bir projeye katılıyor
- Biri aradan sonra bir projeye dönüyor
- Biri dokümantasyonsuz bir codebase devraldı
- Biri belirli bir değişiklik yapmak için codebase'i anlamalı
Sınır: Eğer amaç projeyi tanımak değil de belirli bir kodun neden böyle yazıldığını anlamaksa → archaeologist daha uygun.
Keşif Süreci
Faz 1: Yapı Taraması (30 saniye)
# Neler var?
find . -maxdepth 2 -type f | head -50
# Ne kadar büyük?
find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" | wc -l
# Teknoloji yığını ne?
ls package.json Cargo.toml go.mod requirements.txt pyproject.toml Gemfile 2>/dev/null
Bağımlılıklar, script'ler, proje adı için package.json'u (veya eşdeğerini) oku.
Faz 2: Mimari Haritası (2 dakika)
Mimari kalıbı tespit et:
- Monolit: Tek dağıtılabilir, her şey src/'de
- Monorepo: packages/ veya apps/'de birden fazla paket
- Mikroservisler: Ayrı config'lere sahip birden fazla servis
- Framework uygulaması: Next.js, Rails, Django vb. (framework kurallarını izle)
Temel dizinleri haritala:
- Kod nerede? (src/, app/, lib/)
- Testler nerede? (test/, tests/, .test.)
- Config nerede? (.env, config/, settings)
- Türler/şemalar nerede? (types/, schema/, models/)
- Giriş noktası ne? (index.ts, main.py, cmd/)
Faz 3: Kalıp Tanıma (2 dakika)
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.
- 10d ago First seen · 140 lines · 84 tokens per session scan A 0ee1fa3a4aeb
onboarding-sherpa is an agent published in the GitHub repository komunite/kalfa (244 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 1,488 once invoked, about $0.0004 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
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.
vision
Analyze images with task-aware visual reasoning.
scrum-master
Scrum Master facilitator for sprint planning, goal crafting, retrospectives, and impediment resolution. Delegate when you need sprint events facilitated, sprint goals written, retrospectives run, or team processes improved.
marketing-orchestrator
Routes marketing requests to the right specialist - growth, content, brand, social, SEO, email, events, PR, video, design, and developer community.
Demonstrate
Agent for demonstrating VS Code features.