A project setup wizard scans a codebase, identifies its technology stack, and produces onboarding recommendations. It runs in seven phases and can generate a project improvement plan and readiness score.

Use it when starting with a project, configuring OrchestKit, rescanning an existing codebase, viewing only the readiness score, or generating only the improvement plan.

It gives a new project or team a structured starting point instead of requiring them to inspect the repository and configuration manually. Rescanning helps update the recommendations after major changes.

setup — Command by yonatangross

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/yonatangross/orchestkit/setup

Clone the repo

git clone --depth 1 https://github.com/yonatangross/orchestkit

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

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

Security scan D 2 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.

Model	Per session	Once invoked
Fable 5	$0.00061	$0.04038
Opus 5	$0.00030	$0.02019
Sonnet 5	$0.00012	$0.00808
Haiku 4.5	$0.00006	$0.00404

Measured yesterday against content hash 5864ae37e92e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

setup scanned grade D with 2 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 yesterday.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Check installed vs recommended MCPs by reading `.mcp.json` and `~/.claude/settings.json`. Load `Read("${CLAUDE_PLUGIN_ROOT}/skills/setup/references/stack-skill-mapping.md")` for the MCP recommendation matrix. Present as

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

> **`--dangerously-skip-permissions` policy (CC 2.1.121 + 2.1.126, #1583):** the flag's scope expanded substantially. As of 2.1.126 it bypasses prompts for writes to `.claude/`, `.git/`, `.vscode/`, shell config files (`

plugins/ork/.cursor-plugin/commands/setup.md · 285 lines

How it starts

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

Auto-generated from skills/setup/SKILL.md

Source: https://github.com/yonatangross/orchestkit

OrchestKit Setup Wizard

Personalized onboarding that scans your codebase, detects your stack, recommends skills and MCPs, and generates an actionable improvement plan.

When to Use

First time after installing OrchestKit (/plugin install ork)
Joining a new project and want OrchestKit tuned for it
Periodically with --rescan to track improvement
Enterprise users who need safe, user-scoped install confirmation

Quick Start

/ork:setup              # Full 7-phase wizard
/ork:setup --rescan     # Re-scan after changes (skip safety phase)
/ork:setup --score-only # Just show readiness score
/ork:setup --plan-only  # Just show improvement plan
/ork:setup --configure  # Jump directly to Phase 3.5: project configuration wizard

Argument Resolution

FLAG = "$ARGUMENTS[0]"  # First token: --rescan, --score-only, --plan-only, --channel
# If no arguments, run full 7-phase wizard.
# $ARGUMENTS is the full string (CC 2.1.59 indexed access)

CRITICAL: Task Management is MANDATORY (CC 2.1.16)

BEFORE doing ANYTHING else, create tasks to track progress:

# 1. Create main task IMMEDIATELY
TaskCreate(
  subject="Setup: onboarding wizard",
  description="Personalized setup scanning codebase and configuring OrchestKit",
  activeForm="Running setup wizard"
)

# 2. Create subtasks for key phase groups
TaskCreate(subject="Scan & detect stack", activeForm="Scanning codebase and detecting stack")
TaskCreate(subject="Safety & configure", activeForm="Checking config and running configuration wizard")
TaskCreate(subject="Recommend skills & MCPs", activeForm="Matching stack to skills and MCPs")
TaskCreate(subject="Score & plan", activeForm="Computing readiness score and improvement plan")

# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])
TaskUpdate(taskId="5", addBlockedBy=["4"])

# 4. Update status as you progress
TaskUpdate(taskId="2", status="in_progress")  # When starting
TaskUpdate(taskId="2", status="completed")    # When done

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

yesterday First seen · 285 lines · 61 tokens per session scan D 5864ae37e92e

Subscribe to this mod's changes

setup is a command published in the GitHub repository yonatangross/orchestkit (224 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 4,038 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AI Frontend LLM Planning agents ai-development claude-code claude-plugin langgraph

setup