onboard

onboard is a skill for Claude Code from tranhieutt/software_development_department. It costs 42 tokens per session (543 once invoked), scanned A, original, MIT.

A document generator that summarizes a project's architecture, conventions, important files, recent changes, and current priorities for newcomers.

In plain words
What is it for?
Use it to prepare onboarding material for developers, agents, or other contributors joining an existing project.
Why use it?
It reduces the time new contributors or agents need to understand an unfamiliar codebase and start useful work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it to prepare onboarding material for developers, agents, or other contributors joining an existing project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tranhieutt/software_development_department/onboard
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.

Any agent
npx skills add tranhieutt/software_development_department --skill onboard
Clone the repo
git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

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/tranhieutt/software_development_department/onboard/github.svg)](https://agentmods.dev/skills/tranhieutt/software_development_department/onboard)
Your own site
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/onboard"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/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/tranhieutt/software_development_department/onboard"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 543 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.00042 $0.00543
Opus 5 $0.00021 $0.00271
Sonnet 5 $0.00008 $0.00109
Haiku 4.5 $0.00004 $0.00054

Measured 8d ago against content hash 0c92a15de4a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 8d 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 · 75 lines

What it actually says

When this skill is invoked:

  1. Read the CLAUDE.md for project overview and standards.

  2. Read the relevant agent definition from .claude/agents/ if a specific role is specified.

  3. Scan the codebase for the relevant area:

    • For programmers: scan src/ for architecture, patterns, key files
    • For designers: scan design/ for existing design documents
    • For narrative: scan design/narrative/ for world-building and story docs
    • For QA: scan tests/ for existing test coverage
    • For production: scan production/ for current sprint and milestone
  4. Read recent changes (git log if available) to understand current momentum.

  5. Generate the onboarding document:

# Onboarding: [Role/Area]

## Project Summary
[2-3 sentence summary of what this product is and its current state]

## Your Role
[What this role does on this project, key responsibilities, who you report to]

## Project Architecture
[Relevant architectural overview for this role]

### Key Directories
| Directory | Contents | Your Interaction |
|-----------|----------|-----------------|

### Key Files
| File | Purpose | Read Priority |
|------|---------|--------------|

## Current Standards and Conventions
[Summary of conventions relevant to this role from CLAUDE.md and agent definition]

## Current State of Your Area
[What has been built, what is in progress, what is planned next]

## Current Sprint Context
[What the team is working on now and what is expected of this role]

## Key Dependencies
[What other roles/systems this role interacts with most]

## Common Pitfalls
[Things that trip up new contributors in this area]

## First Tasks
[Suggested first tasks to get oriented and productive]

1. [Read these documents first]
2. [Review this code/content]
3. [Start with this small task]

## Questions to Ask
[Questions the new contributor should ask to get fully oriented]
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. 8d ago First seen · 75 lines · 42 tokens per session scan A 0c92a15de4a2

Subscribe to this mod's changes

onboard is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 543 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-09-03.

Related

Other skills, from other repositories

cm-notebooklm

Sync high-value dev knowledge (skills, decisions, lessons) into Google NotebookLM for cloud recall, podcasts, and flashcards. Pairs with Dockit/deep-search. Use for NotebookLM, nlm, knowledge base, skill sync, or cross-machine AI memory.

tody-agent/codymaster · 60 tokens

ask

Answer a question from this project's own knowledge — retrieved, read and cited, never from memory.

Misaka16384/magi · 21 tokens

compile

Compile raw sources into dense, interlinked reference and concept cards, and mine the concepts a compiled card left implicit.

Misaka16384/magi · 25 tokens

med-mentor

Teach medical personnel (physicians, residents, medical students, nurses, PAs, paramedics) clinical knowledge and skills within this workspace, over multiple sessions, via short interactive HTML lessons. Use this whenever the user wants to study for board exams (USMLE, COMLEX, NCLEX, specialty boards), prepare for…

Premansh12/med-mentor · 153 tokens

baoyu-comic

A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.

JimLiu/baoyu-skills · 61 tokens

skill-creation-walkthrough

Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…

rampstackco/claude-skills · 135 tokens