onboard

An interactive first-run setup wizard for a software project. It detects the project's tools and test commands, checks that commands can run, configures settings, and performs a small test.

In plain words
What is it for?
Use it when setting up a project, switching project types, changing test tools or package managers, or when other SkillFoundry commands use the wrong settings.
Why use it?
It reduces setup mistakes when starting with SkillFoundry or when a project's tools have changed.

Skill for Claude CodeCodex

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.

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

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,938 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.01938
Opus 5 $0.00006 $0.00969
Sonnet 5 $0.00003 $0.00388
Haiku 4.5 $0.00001 $0.00194

Measured 2d ago against content hash 450682e96ae1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

.agents/skills/onboard/SKILL.md · 284 lines

How it starts

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

/onboard — SkillFoundry First-Run Setup

Role: Interactive setup wizard that detects the project stack, verifies shell execution, configures the framework, and walks the user through their first workflow.


Usage

/onboard          First-run or re-run setup
/onboard --reset  Clear all detected state and start fresh
/onboard --quiet  Run detection only, no prompts

When to use

  • First time SkillFoundry is used in a project
  • After switching to a different project type (e.g., added Playwright)
  • When /testloop or /feature reports wrong commands
  • When stack changed (new test framework, new package manager)

Behavior

Execute these steps in order:

Step 1: Welcome

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  SKILLFOUNDRY ONBOARDING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This wizard will:
  1. Detect your project stack and test commands
  2. Verify shell execution is available
  3. Configure framework settings
  4. Run a minimal test to confirm everything works
  5. Show you the two commands you need to start

Takes about 5 minutes. You can run /onboard again any time.

Step 2: Git check

git rev-parse --git-dir >/dev/null 2>&1 || echo "NO_GIT"

If no git repo:

⚠️  No git repository found.
    SkillFoundry requires git for commit tracking and state management.

    Initialize now? (recommended)
    → git init && git add -A && git commit -m "initial commit"

Auto-initialize if user confirms. If user declines, warn that /feature commit stage will not work.

Step 3: Execution context detection

Run agents/_execution-context.md detection algorithm.

Display result clearly:

EXECUTION CONTEXT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Shell access:   ✓ Available
Project root:   ✓ /path/to/project
Mode:           REAL (commands execute and results are verified)

Or if advisory:

Shell access:   ✗ Not available
Mode:           ADVISORY (static analysis only — manual verification required)

To enable real execution: use Claude Code CLI (not the web UI)

Read the full file on GitHub · 284 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. 2d ago First seen · 284 lines · 13 tokens per session scan A 450682e96ae1

Subscribe to this mod's changes

onboard is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,938 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens

ring:applying-composition-patterns

React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…

LerianStudio/ring · 68 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:auditing-dependency-security

Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…

LerianStudio/ring · 102 tokens