Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gustavo-meilus/aiboarding/plugin install aiboardingWrote 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/gustavo-meilus/aiboarding/create-agent-onboarding)<a href="https://agentmods.dev/skills/gustavo-meilus/aiboarding/create-agent-onboarding"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/create-agent-onboarding.svg" alt="Measured on agentmods" 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.00076 | $0.02484 |
| Opus 5 | $0.00038 | $0.01242 |
| Sonnet 5 | $0.00015 | $0.00497 |
| Haiku 4.5 | $0.00008 | $0.00248 |
Grade B, and why
create-agent-onboarding scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`<plugin-root>/templates/settings/hooks.json` into `<repo>/.claude/settings.json`, How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating agent onboarding files
Treat the AI as a fresh engineer. Generate a compressed, high-signal AGENTS.md
at the repo root - the canonical, tool-agnostic onboarding document read natively
by Codex, Copilot, Cursor and imported by Claude Code via a thin CLAUDE.md
wrapper - then bootstrap the lifecycle that keeps it current.
Announce at start: "Using create-agent-onboarding to generate this repo's onboarding files."
Runtime awareness
The generation phases below are tool-agnostic and work under Claude Code, Codex,
Copilot CLI, or any SKILL.md-compatible agent. Phase 6 installs repo-local hooks
only for Claude Code. The Codex plugin supplies optional native hooks after /hooks
trust review; copied standalone skills never install Codex settings. When hooks are
disabled, unavailable, or untrusted, run update-agent-onboarding manually after
meaningful commits.
Phase 0: Pre-flight routing
Inspect the repo root before generating anything:
AIBOARDING.mdexists (legacy v1 layout): stop and runmigrate-aiboardinginstead - never regenerate from scratch over an existing onboarding investment.AGENTS.mdalready exists: treat it as primary input. Skip greenfield grilling; interrogate only the gaps against the section schema below, then propose a restructure as an approval-gated diff. Never overwrite silently.CLAUDE.mdalready exists: preserve it. The only changes allowed are adding the@AGENTS.mdimport line and managing an aiboarding-owned block via.aiboarding/tools/inject-fenced(marker-fenced, idempotent, removable).
Shared contracts
AGENTS.md schema - tool-agnostic, no frontmatter, no Claude-specific syntax.
H2 sections in this exact order:
## Project Purpose## Stack and Runtime## Build, Test, Run- exact commands; fast checks and full checks## Architecture Map- directories, boundaries, data flow, dependency direction## Domain Model- entities, workflows, invariants, vocabulary## Agent Guardrails- what agents must NOT assume/refactor/delete/rename/"simplify"## Known Failure Modes- mistakes previous agents made or will likely make## Verification Before Completion- commands agents must run before claiming done## Escalation - Ask the User When- stop-and-ask cases
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.
- 6d ago First seen · 175 lines · 76 tokens per session scan B 9bc9b8649a2a
create-agent-onboarding is a skill published in the GitHub repository gustavo-meilus/aiboarding (2 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 2,484 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
operating-coding-change
The single Rootloom entry for code changes. Route Direct, Scoped, Governed, Evidence, and external-action work; repair owning invariants, preserve unrelated work, and report only verification that ran.
setup-rootloom
Plan, install, inspect, update, or roll back Rootloom Personal Core in a user's Codex home. Supports Skills-only, guidance, and the recommended personal preset. Use when the user explicitly asks for a Rootloom setup plan, installation, configuration, bootstrap, repair, audit, status, update, reduction, rollback, or…
project-memory
Initialize, retrieve, and explicitly update the separate Rootloom Memory plugin's repository-owned architecture, risk, decision, and failure lessons. Use only when explicitly requested. Memory is experimental, advisory, and outside Rootloom Core.
project-guidance
Seed, refresh, refine, or validate concise evidence-backed AGENTS.md guidance. Deterministic scripts own the managed block; model judgment may add only durable repository-specific invariants outside it.
operating-code-review
Review code, diffs, pull requests, migrations, or architecture without modifying files. Lead with severity-ranked evidence-backed findings, challenge root-cause claims, and disclose cleared and unreviewed scope.
dayu-harness
A one-time deployment tool that adds a project governance system built around AGENTS.md, project instructions, documentation, hooks, continuous integration, and maintenance scripts.