What is onboard-repo?

An interactive setup command for adding a repository to AllBeads, a project system for tracking issues and giving coding agents repository guidance. It can initialize Beads tracking, create a CLAUDE.md guidance file, and add the repository to shared contexts.

Use it to onboard the current or another repository, optionally discover existing issues, and choose which setup steps to skip.

It gathers the repository setup steps in one workflow instead of requiring each tracking and guidance file to be configured separately.

onboard-repo — Command for Claude Code by thrashr888

Install

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.

Claude Code

/plugin marketplace add thrashr888/AllBeads

Claude Code

/plugin install allbeads

Made for: Claude Code.

Or install allbeads, the plugin that ships this one along with the rest of its 1 skill, 19 commands, 1 hook.

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/thrashr888/allbeads/onboard-repo/github.svg)](https://agentmods.dev/commands/thrashr888/allbeads/onboard-repo)

Your own site

<a href="https://agentmods.dev/commands/thrashr888/allbeads/onboard-repo"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/onboard-repo/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/thrashr888/allbeads/onboard-repo"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/onboard-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 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,050 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.00009	$0.01050
Opus 5	$0.00005	$0.00525
Sonnet 5	$0.00002	$0.00210
Haiku 4.5	$0.00001	$0.00105

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

Security

Grade A, and why

onboard-repo 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 11d 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-plugin/commands/onboard-repo.md · 158 lines

How it starts

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

Onboard the current repository (or a specified repository) into the AllBeads ecosystem.

This command runs an interactive workflow that:

Initializes beads tracking (bd init)
Creates a CLAUDE.md file with project guidance
Adds the repository to AllBeads contexts
Optionally runs janitor to discover existing issues
Sets up CI/CD recommendations

Usage:

# Onboard current directory
allbeads onboard-repo

# Onboard specific directory
allbeads onboard-repo /path/to/repo

# Non-interactive mode (use defaults)
allbeads onboard-repo --yes

# Skip specific steps
allbeads onboard-repo --skip-init      # Skip bd init
allbeads onboard-repo --skip-claude    # Skip CLAUDE.md creation
allbeads onboard-repo --skip-context   # Skip adding to contexts

What gets set up:

1. Beads Tracking (.beads/ directory)

Runs bd init to create the .beads/ directory
Initializes issues.jsonl for issue tracking
Sets up local SQLite database

2. CLAUDE.md

Creates a template CLAUDE.md file
Includes project overview section
Pre-fills common development commands
Documents the project structure
Provides guidance for AI agents

3. AllBeads Context

Adds the repository to ~/.config/allbeads/config.yaml
Detects git remote URL automatically
Auto-configures authentication strategy (SSH vs HTTPS)
Makes the repo visible in ab context list

4. Optional: Janitor Analysis

Scans codebase for potential issues
Creates beads for TODO comments
Identifies security concerns
Detects code smells and technical debt

After onboarding:

The repository will be ready for:

Issue tracking with bd create/list/update/close
Multi-context aggregation via ab list/stats
TUI visualization with ab tui
Agent coordination with AllBeads Mail
Cross-repository dependency tracking

Check onboarding status:

ab context onboarding

Example session:

$ cd ~/projects/my-app
$ allbeads onboard-repo

🚀 AllBeads Repository Onboarding

Repository: my-app
Path: /Users/me/projects/my-app
Remote: [email protected]:me/my-app.git

📦 Step 1: Initialize Beads Tracking
  Initialize beads tracking in this repository? [Y/n]: y
  Running: bd init
  ✓ Beads initialized successfully

📝 Step 2: Setup CLAUDE.md
  Create a starter CLAUDE.md file? [Y/n]: y
  ✓ Created CLAUDE.md
  ℹ  Edit CLAUDE.md to add project-specific guidance

🔗 Step 3: Add to AllBeads Contexts
  Add this repository to AllBeads contexts? [Y/n]: y
  ✓ Added to AllBeads contexts as 'my-app'

📚 Next Steps:

1. Create your first issue:
   cd /Users/me/projects/my-app
   bd create --title="Initial setup" --type=task --priority=2

2. View your issues in the TUI:
   ab tui

3. Check onboarding status:
   ab context onboarding

✅ Onboarding complete!

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

11d ago First seen · 158 lines · 9 tokens per session scan A 2d0a89b2bf42

Subscribe to this mod's changes

onboard-repo is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 12d ago), licensed MIT. It adds 9 tokens to every session and 1,050 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-08-31.

Project Management Project management beads issues jira

onboard-repo

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

What gets set up:

1. Beads Tracking (.beads/ directory)

2. CLAUDE.md

3. AllBeads Context

4. Optional: Janitor Analysis

After onboarding:

Example session:

What this file has done since we first saw it

Other commands, from other repositories

pm-status

pm-charter

pm-check

pm-done

_closing

jira-discover-project