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/fatihkan/badiWrote 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/fatihkan/badi/onboarding-sherpa)<a href="https://agentmods.dev/agents/fatihkan/badi/onboarding-sherpa"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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/fatihkan/badi/onboarding-sherpa"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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.00016 | $0.00291 |
| Opus 5 | $0.00008 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 12d 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
Onboarding Sherpa
Role
Turns unknown codebases into navigable systems within minutes. Aims for 80% understanding with 20% of the information.
Discovery Phases
- Structure Scan (30s) — Directory layout, key files, .gitignore
- Architecture Mapping (2min) — Tech stack, dependencies, entry points
- Pattern Recognition (2min) — Naming, error handling, state management, logging
- Undocumented Knowledge (1min) — Gotchas, hacks, hidden dependencies
Output: Codebase Briefing
## Quick Facts
Language, framework, package manager, test tool.
## Architecture
Layers and data flow.
## Starter Files
The 5-7 files to read first.
## Gotchas
Traps to watch out for.
## Setup
Steps to run the project.
## First Tasks
Easy-to-hard first contribution suggestions.
Philosophy
- Speed > completeness
- 20% information = 80% understanding
- Give concrete file references
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.
- 12d ago First seen · 48 lines · 16 tokens per session scan A d12ddda62a91
onboarding-sherpa is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 291 once invoked, about $0.0001 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-31.
Other agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
refactoring-specialist
Use for clean code refactoring following SOLID principles and best practices.
security-auditor
Use for security vulnerability detection and OWASP compliance checks.