onboard

A guided setup skill for preparing a new project for CodingBuddy, an AI coding assistant. It scans files to identify languages, frameworks, tests, monorepo structure, and existing AI-tool settings.

In plain words
What is it for?
It is for detecting a project's technology stack, generating codingbuddy.config.json, setting up adapters, and installing AI rules through interactive questions.
Why use it?
It reduces the manual work of figuring out a project's setup and creating compatible configuration files.

Skill for Claude CodeCodex

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 skills/jeremydev87/codingbuddy/onboard
Any agent
npx skills add JeremyDev87/codingbuddy --skill onboard
Clone the repo
git clone --depth 1 https://github.com/JeremyDev87/codingbuddy

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,280 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.00035 $0.01280
Opus 5 $0.00017 $0.00640
Sonnet 5 $0.00007 $0.00256
Haiku 4.5 $0.00003 $0.00128

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

packages/rules/.ai-rules/skills/onboard/SKILL.md · 151 lines

How it starts

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

Onboard: New Project Setup

Overview

Guide users through setting up codingbuddy in a new project via interactive, step-by-step onboarding. Detect the tech stack automatically, generate configuration, and create adapter files for their AI tools.

Step 1: Project Scanning

Scan the project root to detect:

Package managers & languages:

  • package.json → Node.js/TypeScript (check for typescript dep)
  • requirements.txt / pyproject.toml / setup.py → Python
  • go.mod → Go
  • Cargo.toml → Rust
  • pom.xml / build.gradle → Java/Kotlin
  • Gemfile → Ruby
  • composer.json → PHP

Frameworks (from dependency files):

  • React, Next.js, Vue, Angular, Svelte, Express, NestJS, Django, Flask, FastAPI, Spring Boot, Rails, Laravel, Gin, Echo, etc.

Test setup:

  • Jest, Vitest, Mocha, Pytest, Go test, JUnit, RSpec, PHPUnit, etc.

Monorepo indicators:

  • workspaces in package.json, lerna.json, pnpm-workspace.yaml, nx.json, turbo.json

AI tools already present:

  • .cursor/ → Cursor
  • .claude/ → Claude Code
  • .antigravity/ → Antigravity (Gemini)
  • .codex/ → Codex
  • .q/ → Amazon Q
  • .kiro/ → Kiro
  • .github/copilot/ → GitHub Copilot

After scanning, present findings to the user:

Detected:
- Language: TypeScript
- Framework: Next.js 14, React 18
- Test: Vitest
- Monorepo: Yarn workspaces
- AI tools: .claude/ (existing)

Ask: "Does this look correct? Anything to add or change?" (use AskUserQuestion)

Step 2: Generate codingbuddy.config.json

Based on detected info, generate a draft config:

{
  "language": "en",
  "techStack": {
    "languages": ["typescript"],
    "frameworks": ["nextjs", "react"],
    "testing": ["vitest"],
    "packageManager": "yarn"
  },
  "architecture": {
    "pattern": "layered",
    "monorepo": true
  },
  "agents": {
    "primary": "software-engineer",
    "specialists": ["frontend-developer", "test-engineer"]
  }
}

Ask the user to confirm or adjust:

  • Communication language (en, ko, ja, zh, es, etc.)
  • Primary agent selection (show top 3 recommendations based on tech stack)
  • Architecture pattern (layered, clean, hexagonal, or custom)

Read the full file on GitHub · 151 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 · 151 lines · 35 tokens per session scan A 3224ca1c5f29

Subscribe to this mod's changes

onboard is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 1,280 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

om-integration-builder

Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…

open-mercato/open-mercato · 73 tokens

om-ds-guardian

Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…

open-mercato/open-mercato · 76 tokens

om-integration-tests

Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the om-prepare-test-env skill and attaches to the shared descriptor it writes. Use…

open-mercato/open-mercato · 99 tokens

om-create-agents-md

Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules…

open-mercato/open-mercato · 85 tokens

om-smart-test

Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.

open-mercato/open-mercato · 64 tokens

om-auto-qa-scenarios

Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…

open-mercato/open-mercato · 99 tokens