A repository onboarding command that examines a codebase and records its technology stack, project structure, database-migration setup, and baseline test results. It supports single projects, multi-module Maven builds, and monorepos, which are repositories containing several related applications.

Use it at the beginning of work on a repository to inspect files, detect Spring or other neighboring applications, run the available validation harness, and create onboarding notes.

It gives later development tasks a shared description of an unfamiliar repository and shows the starting state before changes are made.

onboard — Command for Claude Code by loiane

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.

Clone the repo

git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/onboard/github.svg)](https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/onboard)

Your own site

<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/onboard"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/onboard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/onboard"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 727 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00727
Opus 5.5	$0.00008	$0.00291
Sonnet 5.5	$0.00004	$0.00145
Haiku 4.5	$0.00002	$0.00073

Measured 2mo ago against content hash e423be4e3cec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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/onboard.md · 48 lines

How it starts

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

/onboard

Phase: 0 — bootstrap Owning agent: .claude/agents/spring-onboarding.md Skills used: brownfield-onboarding, maven-harness-pom, flyway-or-liquibase-detection, harness-report-parsing, archunit-rules

Purpose

Inspect the repository, classify it as greenfield or brownfield, capture a baseline harness run, and produce .specs/_onboarding.md so future commands know the stack.

Inputs

None required. Optional argument: a path to constrain the scan.

For a single-project repo: omit the argument; the script reads ./pom.xml.
For a multi-module Maven build: pass the submodule directory.
For a polyglot monorepo (e.g. Spring Boot backend + Angular/React frontend in sibling top-level dirs): pass the Maven module directory (e.g. shoply-api). Sibling non-JVM apps are auto-detected and recorded under siblings in _stack.json and as context-only notes in _onboarding.md. The harness only validates the Maven module; frontend tooling is owned by its own pipeline.

Reads

pom.xml (root and any submodules)
src/main/**, src/test/** (counts only)
db/migration/**, db/changelog/**
Existing .specs/ if any

Writes

.specs/_onboarding.md
.specs/_stack.json (output of .github/scripts/detect-stack.sh)
.specs/_baseline.json (only if any test exists; output of .github/scripts/harness.sh --baseline)

Process

Resolve the Maven module path (MODULE = optional arg, else .). Run .github/scripts/detect-stack.sh "$MODULE/pom.xml" > .specs/_stack.json. Refuse to proceed if migration == "both".
Count source/test files under $MODULE/src/; classify:
- Greenfield if no src/main/java/** or only the Spring Boot Application.java (auto-generated *ApplicationTests.java and Testcontainers*.java scaffolding do not change the classification).
- Brownfield otherwise.
If brownfield, run .github/scripts/harness.sh --module "$MODULE" --baseline and capture results. Do NOT attempt to fix failures.
Diff $MODULE/pom.xml against .claude/maven/parent-pom-fragment.xml; list missing harness layers as Findings.
Write .specs/_onboarding.md covering: classification, module path, sibling apps (if any), stack JSON, baseline gate results (or “N/A — greenfield”), missing layers, recommended /spec starting point.

Read the full file on GitHub · 48 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.

2mo ago First seen · 48 lines · 19 tokens per session scan A e423be4e3cec

Subscribe to this mod's changes

onboard is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 19d ago), licensed MIT. It adds 19 tokens to every session and 727 once invoked, about $0.0001 per session on Opus 5.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.

Java Planning TDD angular github-copilot spec-driven-development spring-boot

onboard

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/onboard

Purpose

Inputs

Reads

Writes

Process

What this file has done since we first saw it

Other commands, from other repositories

spec-impl

benchmark

profile

update-issue

create-diagram

devkit.github.review-pr