Borrowing it
Nothing to install: this file belongs to me2resh/apexyard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/me2resh/apexyard/main/.claude/skills/onboard/SKILL.mdgit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/onboard)<a href="https://agentmods.dev/skills/me2resh/apexyard/onboard"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/onboard.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 441 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00043 | $0.05182 |
| Opus 5 | $0.00022 | $0.02591 |
| Sonnet 5 | $0.00009 | $0.01036 |
| Haiku 4.5 | $0.00004 | $0.00518 |
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/onboard — Guided First-Run Onboarding
This is increment 1 of the guided-onboarding walking skeleton (technical
design: docs/technical-designs/onboarding-increment-1.md, ticket #910),
now layered with increment 2's depth adaptivity (technical design:
docs/technical-designs/onboarding-increment-2.md § D2/D7, ticket #914).
/onboard is a thin orchestrator + router, not a replacement for
/setup or /handover — it sequences those two skills (plus /feature)
behind a capability tour and an explicit branch. It never edits /setup,
/handover, or /feature; their direct and scripted behaviour stays
byte-for-byte unchanged (see AgDR-0097).
This flow now renders in one of two depth modes — terse or guided
— off a single shared session marker, not a forked skill (US-5/FR-6).
Terse renders every step exactly as increment 1 did (byte-for-byte
identical output — NFR Backward-compat). Guided adds one short
"why this matters" framing sentence after each major step. Depth mode
changes only explanatory narration — it never changes which gate
fires, which approval is required, or any role boundary (the
"presentation only" invariant, mechanically guarded by
.claude/hooks/tests/test_depth_mode.sh's invariant case). See Step 3.5
below for derivation, and "Depth mode override + transparency" for the
mid-session override (FR-6) and the "what mode am I in?" affordance
(FR-9).
The per-term teach-in-context glossary + just-in-time asides (#913) are
now wired into this flow. In guided mode, the first time this skill
uses one of the five core terms — issue/ticket, PR, merge, branch, CI —
toward the adopter, it weaves in a short inline parenthetical explaining
it, once per term per session (design § D3). See "Just-in-time glossary
asides" below for the mechanism. Terse mode sees zero asides — this is
structural, not a formatting choice (the same $mode gate Step 3.5
derives). The ambient any-session lookup + full /tutorial glossary
render (#915) is still a sibling ticket, not yet built as of this
ticket — asking "what's a merge?" outside a guided /onboard run isn't
wired up yet.
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.
- 7d ago First seen · 491 lines · 43 tokens per session scan A f78fb99524ee
onboard is a skill published in the GitHub repository me2resh/apexyard (499 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 5,182 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.