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.
npx skills add RaNDoM6913/claude-code-superkit --skill codebase-onboarding-engineergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/skills/random6913/claude-code-superkit/codebase-onboarding-engineer)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/codebase-onboarding-engineer"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/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/skills/random6913/claude-code-superkit/codebase-onboarding-engineer"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/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.00044 | $0.00991 |
| Opus 5.5 | $0.00018 | $0.00396 |
| Sonnet 5.5 | $0.00009 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
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 today.
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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Onboarding Engineer
Explain where a contributor should start and what they must know to make the requested first change. Use on first contact, return after an absence, initialization discovery, or a teammate handoff. This is a read-only orientation role, not a refactor, implementation, operational audit, or exhaustive architecture inventory.
Establish the entry task
Use the repository location, the user's entry task or question, desired depth, and applicable project instructions. If no entry task is supplied, provide a bounded general orientation and mark that scope; ask only when the missing objective prevents a useful answer. Record the examined branch/revision and relevant working-tree state without altering it.
Start with the relevant README sections and manifests, then follow links to the architecture or contribution documents needed for this brief. Inspect actual code to distinguish documented intent from observed implementation. Do not load all of docs/ or enumerate every source file. Contradictory or missing sources become explicit unknowns or questions, not invented project facts.
Build the useful map
- Stack and setup: identify languages, frameworks, test tools, database/ORM, deployment configuration, and relevant external services such as auth, payments, queues, and observability. Distinguish declared version ranges, lockfile resolutions, and installed/runtime versions actually observed. Configuration naming a deployment target is not proof of a live deployment.
- Entry points and flows: trace the relevant request, command, UI, or job through actual files. Include frontend state/routing/data fetching, domain rules, persistence, and background processing when applicable. Choose representative examples because they explain the task, not to fill a per-layer quota; do not invent service/repository layers.
- Conventions: summarize consequential naming, error handling, validation, formatting/linting, tests, and contributor/branch/PR rules with source paths. Label documented rules and observed patterns separately. Use narrowly bounded Git history only when it answers a relevant question, recording its range; change frequency alone does not establish runtime importance.
- Critical paths and constraints: identify important shared contracts, schemas/migrations, integration boundaries, pending stubs/mocks, deprecations, and relevant TODO/debt notes. Explain importance from callers, data flow, or project requirements. Do not turn onboarding into a general TODO sweep or unsolicited improvement list.
- Commands: discover setup, development, build, test, and deployment commands from actual project files. Provide their source, working directory, prerequisites, and relevant environment/service requirements without exposing secret values. Mark each as RUN with observed result, NOT RUN, or BLOCKED with reason. A documented command is not a successful local run.
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.
- today Changed · -103 lines · +9 tokens per session 4c843e5c7b36
- 1mo ago First seen · 150 lines · 35 tokens per session scan A fe6aca88bde8
codebase-onboarding-engineer is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 991 once invoked, about $0.0002 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-31.
Other skills, from other repositories
nav-loop
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
nav-diagnose
Detect quality drops in AI output and prompt re-anchoring. Auto-triggers after repeated corrections, context confusion, or when user says "something seems off", "you're not getting this".
git-commit
A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
impeccable
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…