claude-init: Skill for Claude Code

.claude/skills/onboard/SKILL.md

onboard is a skill for Claude Code from yash-gadodia/claude-init. It costs 45 tokens per session (650 once invoked), scanned A, original, MIT.

A quick onboarding workflow that builds a mental model of an existing codebase, including its structure, architecture, data, APIs, and frontend.

In plain words
What is it for?
Use it when joining a project or investigating an area such as authentication, payments, APIs, databases, routes, components, or state management.
Why use it?
It reduces the time needed to understand an unfamiliar repository and shows how its major parts connect.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

This is yash-gadodia/claude-init's own configuration. It tells Claude Code how to work on claude-init itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-init configures →

Part of the claude-init plugin — 11 skills, 1 command, 7 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to yash-gadodia/claude-init. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yash-gadodia/claude-init/main/.claude/skills/onboard/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yash-gadodia/claude-init

Made for: Claude Code.

Or install claude-init, the plugin that ships this one along with the rest of its 11 skills, 1 command, 7 agents.

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

agentmods badge for onboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/yash-gadodia/claude-init/onboard/github.svg)](https://agentmods.dev/skills/yash-gadodia/claude-init/onboard)
Your own site
<a href="https://agentmods.dev/skills/yash-gadodia/claude-init/onboard"><img src="https://agentmods.dev/badge/skills/yash-gadodia/claude-init/onboard/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.

agentmods 80×15 button for onboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/yash-gadodia/claude-init/onboard"><img src="https://agentmods.dev/badge/skills/yash-gadodia/claude-init/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 650 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00650
Opus 5 $0.00023 $0.00325
Sonnet 5 $0.00009 $0.00130
Haiku 4.5 $0.00005 $0.00065

Measured 10d ago against content hash f799f0b8a2cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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

.claude/skills/onboard/SKILL.md · 89 lines

How it starts

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

Onboard: Get Up to Speed Fast

You are onboarding to this codebase. Your goal is to build a complete mental model and share it concisely.

If $ARGUMENTS is provided, focus on that area (e.g., "auth", "payments", "API layer").

Process

Phase 1: Structural Scan (use subagents in parallel)

Agent 1 — Architecture:

  • Read CLAUDE.md, ARCHITECTURE.md, README, any docs/ directory
  • Map the directory tree (top 3 levels)
  • Identify framework, language, key dependencies

Agent 2 — Data Layer:

  • Find schema files (Prisma, migrations, models)
  • Map entities and relationships
  • Identify the ORM/query layer

Agent 3 — API Surface:

  • Find route definitions, controllers, resolvers
  • Map endpoints/operations to handlers
  • Identify auth middleware, validation

Agent 4 — Frontend (if applicable):

  • Map pages/routes to components
  • Identify state management
  • Find shared UI components

Phase 1.5: ARCHITECTURE.md Freshness Check

If ARCHITECTURE.md exists:

  • Compare its Directory Structure section against the actual top-level directories
  • Check if modules/services mentioned still exist
  • Check if new top-level directories have appeared that aren't documented
  • If stale sections are found, flag them in the output and offer to update ARCHITECTURE.md

If ARCHITECTURE.md does NOT exist:

  • Note this as a gap in the output
  • Suggest running /claude-init or /update to generate one

Phase 2: Pattern Extraction

From the codebase, identify:

  1. The happy path: How does a typical request flow from user action to database and back?
  2. Error handling pattern: How are errors caught, logged, and surfaced?
  3. Auth pattern: How is authentication/authorization enforced?
  4. Testing pattern: What's tested, what's not, how to run tests?
  5. Deploy pattern: How does code get to production?

Phase 3: Output

Present a concise onboarding doc:

# [Project Name] — Onboarding

## What This Does
<1-2 sentences>

## Stack
<language, framework, DB, key deps>

## Architecture
<ASCII diagram or bullet-point flow>

## Key Patterns
<The 3-5 most important patterns to follow>

## Where Things Live
<Map of important directories/files>

## How to Run
<Dev server, tests, build, deploy commands>

## Gotchas
<Non-obvious things that will trip you up>

Read the full file on GitHub · 89 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.

  1. 10d ago First seen · 89 lines · 45 tokens per session scan A f799f0b8a2cd

Subscribe to this mod's changes

onboard is a skill published in the GitHub repository yash-gadodia/claude-init (5 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 650 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.