repo-onboard

repo-onboard is a command for Claude Code from basher83/lunar-claude. It costs 7 tokens per session (1,697 once invoked), scanned A, original, MIT.

A repository setup command that detects a project's technologies and applies the appropriate configuration steps. A repository is the folder containing a project's code and version-control history.

In plain words
What is it for?
Use it to onboard Python, Rust, Bun or TypeScript, Terraform, and Ansible repositories, including projects that combine several technologies.
Why use it?
It removes the manual work of identifying project types and setting up shared development tools, including migration from pre-commit when relevant.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the repo-forge plugin — 1 skill, 1 command shipped together

Good fit Use it to onboard Python, Rust, Bun or TypeScript, Terraform, and Ansible repositories, including projects that combine several technologies.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/basher83/lunar-claude/repo-onboard
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/basher83/lunar-claude

Made for: Claude Code.

Or install repo-forge, the plugin that ships this one along with the rest of its 1 skill, 1 command.

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.

agentmods badge for repo-onboard

README.md
[![agentmods](https://agentmods.dev/badge/commands/basher83/lunar-claude/repo-onboard/github.svg)](https://agentmods.dev/commands/basher83/lunar-claude/repo-onboard)
Your own site
<a href="https://agentmods.dev/commands/basher83/lunar-claude/repo-onboard"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/repo-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.

agentmods 80×15 button for repo-onboard

Your own site · 80×15
<a href="https://agentmods.dev/commands/basher83/lunar-claude/repo-onboard"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/repo-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,697 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.01697
Opus 5 $0.00003 $0.00848
Sonnet 5 $0.00001 $0.00339
Haiku 4.5 $0.00001 $0.00170

Measured 7d ago against content hash 781109b92cd3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

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

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.

plugins/devops/repo-forge/commands/repo-onboard.md · 156 lines

How it starts

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

Repo Onboard

Detect project type, run the appropriate mise preset chain, and migrate from pre-commit to hk if applicable.

Current State

  • Working directory: !pwd
  • Git repo: !test -d .git && echo "Yes" || echo "No"
  • Existing mise.toml: !test -f mise.toml && echo "Yes" || echo "No"
  • Existing hk.pkl: !test -f hk.pkl && echo "Yes" || echo "No"
  • Pre-commit config: !test -f .pre-commit-config.yaml && echo "Yes (migration candidate)" || echo "No"

Phase 1: Detect Project Type

Scan for project type indicators using Glob:

  • pyproject.toml, setup.py, setup.cfg → Python
  • Cargo.toml → Rust
  • package.json, bun.lock, bun.lockb, tsconfig.json → Bun/TypeScript
  • *.tf files in the current or immediate subdirectories → Terraform
  • ansible.cfg, playbooks/ directory, roles/ directory → Ansible

A project may match multiple types (e.g., Python + Terraform monorepo). Track all matches. If nothing matches, the project is "base only".

Phase 2: Confirm with User

Confirm the detected configuration.

Build the question dynamically based on what was detected:

If project type(s) detected, present them. If .pre-commit-config.yaml exists, include migration in the confirmation. If hk.pkl already exists, note it will be overwritten.

Question format:

  • header: "Onboard"
  • question: "Detected: [type(s)]. [Migration note if applicable]. This will run preset:base + preset:[type], creating mise.toml, hk.pkl, .editorconfig, cliff.toml, .gitignore, and renovate.json. Proceed?"
  • options:
    • Proceed (Run detected preset chain)
    • Base only (Skip language preset, run preset:base only)
    • Cancel (Abort onboarding)

If multiple types detected, use multiSelect: true to let user choose which language presets to apply.

Phase 3: Execute Presets

Based on user confirmation, run the appropriate preset via Bash.

Available presets and their commands:

  • Python: mise preset:uv (depends on preset:base, runs both)
  • Rust: mise preset:rust (depends on preset:base, runs both)
  • Bun/TypeScript: mise preset:bun (depends on preset:base, runs both)
  • Terraform: mise preset:terraform (depends on preset:base, runs both)
  • Ansible: mise preset:ansible (depends on preset:base, runs both)
  • Base only: mise preset:base

Read the full file on GitHub · 156 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. 7d ago First seen · 156 lines · 7 tokens per session scan A 781109b92cd3

Subscribe to this mod's changes

repo-onboard is a command published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,697 once invoked, about $0.0000 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-09-03.