What is codebase-onboarding-engineer?

An onboarding skill that creates a short first-pass map of an unfamiliar codebase. A codebase is the project’s source code and supporting files; the map covers its technologies, structure, conventions, important paths, and known limits.

Use it when first opening a repository, returning after a long absence, or preparing guidance for another contributor or agent. It is for understanding the current project, not proposing refactors.

It helps a new contributor understand where to make a change without producing a large architecture document. It bases its notes on files such as README.md, project manifests, and contributor guides.

codebase-onboarding-engineer — Skill by RaNDoM6913

Install

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.

agentmods

npx agentmods add skills/random6913/claude-code-superkit/codebase-onboarding-engineer

Any agent

npx skills add RaNDoM6913/claude-code-superkit --skill codebase-onboarding-engineer

Clone the repo

git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkit

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,279 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00035	$0.01279
Opus 5	$0.00017	$0.00639
Sonnet 5	$0.00007	$0.00256
Haiku 4.5	$0.00003	$0.00128

Measured yesterday against content hash fe6aca88bde8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

packages/codex/skills/codebase-onboarding-engineer/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codebase Onboarding Engineer

Produce a concise onboarding brief in 30-60 minutes for an unfamiliar codebase. Output is what a new contributor needs to make their first useful change — not an exhaustive architecture document.

Phase 0: Load Project Context

Read if exists:

README.md — project purpose, install / run instructions
AGENTS.md / CLAUDE.md — declared conventions
package.json / pyproject.toml / go.mod / Cargo.toml — dependencies, scripts
docs/, ARCHITECTURE.md, CONTRIBUTING.md — pre-written guidance

When to Use

First contact with a new repository
Before starting work after a long absence or as a new hire
When /superkit-init runs on an unfamiliar codebase
Before recommending architectural changes — understand current state first
Preparing a brief for a teammate or another agent

What NOT to Do

Do not write an exhaustive 50-page architecture doc — this is an onboarding brief
Do not speculate about intent — note what code does, mark assumptions
Do not suggest refactors during onboarding
Do not make claims you can't back with a file path

Workflow

Step 1: Surface Map (10 min)

Top-level directories — what they hold
Entry points — main.*, index.*, cmd/*, executables in package.json scripts
Test directories — how to run tests
CI / build / deploy — .github/workflows/, Dockerfile, Makefile

Step 2: Tech Stack (5 min)

Language(s) + version
Framework(s) (web, ORM, test runner, CSS)
Database(s) + ORM
Deployment target (cloud, container, edge)
Key third-party services (auth, payment, queue, observability)

Step 3: Architecture Layers (15 min)

HTTP / API layer — how a request enters
Service / business logic — where rules live
Persistence — DB access pattern (repository / direct / ORM)
Frontend (if applicable) — state, routing, data fetching
Background work — jobs, queues, schedulers

For each layer, identify 1-2 representative files as canonical examples.

Read the full file on GitHub · 150 lines

Changes

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.

yesterday First seen · 150 lines · 35 tokens per session scan A fe6aca88bde8

Subscribe to this mod's changes

codebase-onboarding-engineer is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,279 once invoked, about $0.0002 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.

Data and AI Planning ai-agents anthropic claude-code codex-cli context-engineering developer-tools

apm-review-panel

Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…

microsoft/apm · 178 tokens

apm-issue-autopilot

Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…

microsoft/apm · 238 tokens

apm-spec-guardian

Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…

microsoft/apm · 215 tokens

apm-triage-panel

Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.

microsoft/apm · 59 tokens

batch-bug-shepherd

Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…

microsoft/apm · 227 tokens

cli-logging-ux

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…

microsoft/apm · 94 tokens