onboard

A codebase-onboarding command that scans an existing project and records its conventions, constraints, and technology profile.

In plain words
What is it for?
Use it to create a reusable project profile from the codebase, including its structure, rules, and observed implementation practices.
Why use it?
It reduces the time needed to understand an unfamiliar repository before making changes.

Command for Claude Code

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 commands/zts0hg/codexspec/onboard
Clone the repo
git clone --depth 1 https://github.com/Zts0hg/codexspec

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,114 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.00015 $0.02114
Opus 5 $0.00008 $0.01057
Sonnet 5 $0.00003 $0.00423
Haiku 4.5 $0.00002 $0.00211

Measured 2d ago against content hash 44f8a69beec9, 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.

.claude/commands/codexspec/onboard.md · 90 lines

How it starts

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

Codebase Onboarding

Language Preference

Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):

  • Interaction language (language.interaction): language for all conversation with the user — questions, explanations, status messages, and codexspec CLI terminal output.
  • Document language (language.document): language for generated artifact files (the profile records).

Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language. Exception: evidence.facts records a verbatim code observation (path + snippet) and MUST NOT be translated.

User Input

$ARGUMENTS

Role and Operating Model

onboard is the cold-start / bulk counterpart to distill. Where distill writes the project profile incrementally from interaction, onboard scans an existing codebase once and batch-writes the reusable knowledge that is implicit in the code and not already recorded accessibly into the shared store .codexspec/profile/. It exists to bootstrap a brownfield project's profile so accumulated project knowledge is grounded immediately, instead of only after enough work has flowed through distill.

onboard is read-only on the codebase and write-only to .codexspec/profile/: it never modifies source, tests, git state, or the constitution. It is a standalone, user-invoked command — not an SDD pipeline stage: it has no auto-next successor and no automatic hook, and it leaves no persistent document beyond the profile records (no map, no walkthrough — those, if ever wanted, belong to a separate explain).

Prerequisite & Scaffold

Before scanning:

  • If .codexspec/ is absent, the project is not codexspec-initialized. Stop and direct the user to run codexspec init. Do not scaffold a whole project.
  • If .codexspec/ is present but the profile store is missing, ensure the canonical scaffold — the six category directories .codexspec/profile/{constraints,conventions,pitfalls,decisions,strategies,runbooks}/ (matching what codexspec init produces) — before writing.
  • git is not required. onboard runs on a plain directory.

Read the full file on GitHub · 90 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 · 90 lines · 15 tokens per session scan A 44f8a69beec9

Subscribe to this mod's changes

onboard is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 2,114 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-31.