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 gustavo-meilus/aiboarding --skill migrate-aiboardinggit clone --depth 1 https://github.com/gustavo-meilus/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/migrate-aiboarding)<a href="https://agentmods.dev/skills/gustavo-meilus/aiboarding/migrate-aiboarding"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/migrate-aiboarding.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.00070 | $0.01148 |
| Opus 5 | $0.00035 | $0.00574 |
| Sonnet 5 | $0.00014 | $0.00230 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade B, and why
migrate-aiboarding 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
In `<repo>/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating AIBOARDING.md → AGENTS.md + CLAUDE.md
One-shot migration from the v1 custom-injection layout to the standard-files
layout. The onboarding knowledge in AIBOARDING.md is an investment - carry it
over; never regenerate from scratch and never delete anything without approval.
Announce at start: "Using migrate-aiboarding to move this repo to the AGENTS.md layout."
Precondition: AIBOARDING.md exists at the repo root. If it does not, stop and
suggest create-agent-onboarding. If AGENTS.md also already exists, stop and ask
the user which file is authoritative before writing anything.
Step 1: Carry over state
Read the AIBOARDING.md frontmatter (aiboarding_version, generated,
last_synced_commit). These seed .aiboarding/state.json:
aiboarding_version: 2generated: today's datelast_synced_commit: carried over verbatim (empty stays empty - the repair semantics of an empty pointer are preserved).
Step 2: Map the body
Map the three v1 H1 sections onto the v2 schema (see create-agent-onboarding's Shared contracts for the exact section list and order):
| v1 source | v2 target sections |
|---|---|
# 1. Engineering Basics |
Stack and Runtime, Build, Test, Run, Architecture Map |
# 2. Domain & Business Logic |
Project Purpose, Domain Model |
# 3. AI-Specific Context |
Agent Guardrails, Known Failure Modes |
Preserve the compressed density of the source text; split it, don't rewrite it. Backtick-quote any command, identifier, path, or error string that isn't already.
Two v2 sections have no v1 source: Verification Before Completion and
Escalation - Ask the User When. Run a short, scoped grilling pass (the
one-question-at-a-time style from create-agent-onboarding) ONLY for these gaps.
Step 3: Generate the wrapper and lifecycle files
Follow create-agent-onboarding Phase 6: CLAUDE.md (@AGENTS.md + fenced
Claude-notes block), state.json, config.json, .aiboarding/.gitignore, the six
hook files, and its complete current tool set including write-evidence.
Repo-local hook/settings steps are Claude Code-only. Codex plugin hooks are native,
optional, and require /hooks trust review; standalone skills use manual
update-agent-onboarding after meaningful commits.
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 · 83 lines · 70 tokens per session scan B 3944f84dbe5b
migrate-aiboarding is a skill published in the GitHub repository gustavo-meilus/aiboarding (2 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 1,148 once invoked, about $0.0003 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.