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 airvalona/antigravity-like-claude-code --skill team-onboardinggit clone --depth 1 https://github.com/airvalona/antigravity-like-claude-codeWrote 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/airvalona/antigravity-like-claude-code/team-onboarding)<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.
<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>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.00065 | $0.00415 |
| Opus 5 | $0.00032 | $0.00208 |
| Sonnet 5 | $0.00013 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
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 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.
What it actually says
/team-onboarding — Ramp-Up Guide Generator
Port of Claude Code's /team-onboarding.
Steps
-
Gather context
- Read
AGENTS.mdif present (run theinitskill 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 itsdescription. - 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.examplefiles.
- Read
-
Produce
ONBOARDING.mdwith:
# 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">
- 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.
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.
- 10d ago First seen · 53 lines · 65 tokens per session scan A cc59d8534066
team-onboarding is a skill published in the GitHub repository airvalona/antigravity-like-claude-code (2 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 415 once invoked, about $0.0003 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.