team-onboarding

team-onboarding is a skill for Claude Code, Codex from airvalona/antigravity-like-claude-code. It costs 65 tokens per session (415 once invoked), scanned A, original, MIT.

An onboarding-document generator for software projects. It examines project instructions, installed agent skills, recent Git commits, folders, and setup files, then writes a guide for a new developer.

In plain words
What is it for?
Use it when a new teammate needs to get up to speed on a project. It produces an ONBOARDING.md file based on the repository's actual files and history.
Why use it?
It removes the need for someone to manually gather scattered project knowledge for a newcomer. The guide explains setup, code layout, conventions, recent work, and where to begin.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; mentions AGENTS.md.

Good fit Use it when a new teammate needs to get up to speed on a project. It produces an ONBOARDING.md file based on the repository's actual files and history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/airvalona/antigravity-like-claude-code/team-onboarding
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 airvalona/antigravity-like-claude-code --skill team-onboarding
Clone the repo
git clone --depth 1 https://github.com/airvalona/antigravity-like-claude-code

Made for: Claude Code, Codex.

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 team-onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/team-onboarding/github.svg)](https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/team-onboarding)
Your own site
<a href="https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/team-onboarding"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/team-onboarding/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 team-onboarding

Your own site · 80×15
<a href="https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/team-onboarding"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/team-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 415 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.00065 $0.00415
Opus 5.5 $0.00026 $0.00166
Sonnet 5.5 $0.00013 $0.00083
Haiku 4.5 $0.00006 $0.00042

Measured 2mo ago against content hash cc59d8534066, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

team-onboarding 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 2mo 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.

skills/team-onboarding/SKILL.md · 53 lines

What it actually says

/team-onboarding — Ramp-Up Guide Generator

Port of Claude Code's /team-onboarding.

Steps

  1. Gather context

    • Read AGENTS.md if present (run the init skill first if it doesn't exist and the user confirms they want it generated).
    • List installed project-level skills (.agent/skills/*/SKILL.md) and summarize what each one does in one line, pulled from its description.
    • Pull the last ~20 commits (git log --oneline -20) to identify recent areas of active work.
    • Note any CI config, environment setup scripts, or .env.example files.
  2. Produce ONBOARDING.md with:

# Onboarding: <project name>

## What this project does
<short description>

## Getting set up
<install/env steps, pulled from real scripts/config, not invented>

## Codebase map
<key directories and their purpose>

## Conventions
<from AGENTS.md>

## Useful agent skills available
<one line per skill>

## Recent activity
<2-3 sentence summary of what's been actively worked on lately, from git log>

## Where to start
<a concrete first task suggestion, e.g. "run the test suite", "read X module">
  1. Keep it scannable — a new teammate should be productive after a 10-minute read, not handed a full architecture document.

Notes

Base everything on what's actually in the repo. If setup steps aren't documented anywhere, say "setup steps not found — ask a teammate" rather than guessing.

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. 2mo ago First seen · 53 lines · 65 tokens per session scan A cc59d8534066

Subscribe to this mod's changes

team-onboarding is a skill published in the GitHub repository airvalona/antigravity-like-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 415 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens