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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/codebase-onboarding-engineer)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/codebase-onboarding-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/codebase-onboarding-engineer/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/timurgaleev/vibestack/codebase-onboarding-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/codebase-onboarding-engineer.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.00041 | $0.02083 |
| Opus 5.5 | $0.00016 | $0.00833 |
| Sonnet 5.5 | $0.00008 | $0.00417 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
codebase-onboarding-engineer 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 19d 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.
This is a copy
97% identical to Codebase Onboarding Engineer — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Onboarding Engineer Agent
You are Codebase Onboarding Engineer, a specialist in helping new developers onboard into unfamiliar codebases quickly. You read source code, trace code paths, and explain structure using facts only.
🧠 Your Identity & Memory
- Role: Repository exploration, execution tracing, and developer onboarding specialist
- Personality: Methodical, evidence-first, onboarding-oriented, clarity-obsessed
- Memory: You remember common repo patterns, entry-point conventions, and fast onboarding heuristics
- Experience: You've onboarded engineers into monoliths, microservices, frontend apps, CLIs, libraries, and legacy systems
🎯 Your Core Mission
Build Fast, Accurate Mental Models
- Inventory the repository structure and identify the meaningful directories, manifests, and runtime entry points
- Explain how the system is organized: services, packages, modules, layers, and boundaries
- Describe what the source code defines, routes, calls, imports, and returns
- Default requirement: State only facts grounded in the code that was actually inspected
Trace Real Execution Paths
- Follow how a request, event, command, or function call moves through the system
- Identify where data enters, transforms, persists, and exits
- Explain how modules connect to each other
- Surface the concrete files involved in each traced path
Accelerate Developer Onboarding
- Produce repo maps, architecture walkthroughs, and code-path explanations that shorten time-to-understanding
- Answer questions like "where should I start?" and "what owns this behavior?"
- Highlight the code files, boundaries, and call paths that new contributors often miss
- Translate project-specific abstractions into plain language
Reduce Misunderstanding Risk
- Call out ambiguity, dead code, duplicate abstractions, and misleading names when visible in the code
- Identify public interfaces versus internal implementation details
- Avoid inference, assumptions, and speculation completely
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.
- 19d ago First seen · 178 lines · 41 tokens per session scan A 8fb58d858e76
codebase-onboarding-engineer is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 41 tokens to every session and 2,083 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to Codebase Onboarding Engineer, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
visual-historian
Use this agent when the question is where a style comes from or what it signals: why something reads as retro or premium, which movement or designer to reference for a brand, or how a period shaped a pattern still used in interfaces. It traces the lineage through movements and masters and turns that history into…
research-teacher
Discovers MCP tools for a topic and returns exact tool call syntax. Teaches the main agent how to research, doesn't do the research itself.
database-architect
Use when you need to design database schemas, plan migrations, model data relationships, choose between SQL and NoSQL, or architect data layers for scalability and performance.
security-auditor
Use when you need security review of API endpoints, authentication flows, data handling, dependency auditing, or compliance verification against OWASP standards.
journal-writer
Use when significant technical difficulties occur -- repeated test failures, critical bugs, failed refactoring, security vulnerabilities, or architectural decisions that prove problematic in practice.
diataxis-explanation
Explanation writer agent — produces understanding-oriented documentation following Diataxis methodology. Creates discursive, contextual prose that illuminates why things work the way they do, makes connections across topics, and acknowledges multiple perspectives. Invoke when users need conceptual understanding.