GENesis-AGI: Command for Claude Code

.claude/commands/setup.md

setup is a command for Claude Code from WingedGuardian/GENesis-AGI. It costs 61 tokens per session (844 once invoked), scanned B, original, MIT.

A first-run setup and repair command for the Genesis system. It checks whether installation finished and whether initial configuration has been completed, then chooses the needed path.

In plain words
What is it for?
Use it to repair an interrupted installation, complete first-time onboarding, or refresh an already configured setup.
Why use it?
It distinguishes a broken or incomplete installation from an installed system that has not yet been configured, preventing onboarding from running in the wrong state.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Claude Code.

This is WingedGuardian/GENesis-AGI's own configuration. It tells Claude Code how to work on GENesis-AGI itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything GENesis-AGI configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/setup_claude_config.py # .mcp.json only.

Reuse

Borrowing it

Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/WingedGuardian/GENesis-AGI/main/.claude/commands/setup.md
Clone the repo
git clone --depth 1 https://github.com/WingedGuardian/GENesis-AGI

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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/setup/github.svg)](https://agentmods.dev/commands/wingedguardian/genesis-agi/setup)
Your own site
<a href="https://agentmods.dev/commands/wingedguardian/genesis-agi/setup"><img src="https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/setup/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 setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/wingedguardian/genesis-agi/setup"><img src="https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 844 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00061 $0.00844
Opus 5.5 $0.00024 $0.00338
Sonnet 5.5 $0.00012 $0.00169
Haiku 4.5 $0.00006 $0.00084

Measured 1mo ago against content hash 492276c937ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

setup scanned grade B with 1 finding 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 1mo 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.

Reads agent configuration directoriesmediumAgent snooping

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

python scripts/setup_claude_config.py --global # also update ~/.claude/settings.json
.claude/commands/setup.md · 80 lines

How it starts

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

Genesis Setup

/setup covers two jobs — finishing/repairing the install and running first-run onboarding — and routes between them from the system's actual state. Detect first, then route; do not assume.

Step 1 — Detect state

Two independent signals:

  • Infrastructure — did the Layer-1 install (bootstrap.sh / install.sh) actually finish? An interrupted install leaves the venv or dependencies incomplete, and the ~/.genesis/setup-complete marker absent (it is written only at the very end). Check that the venv exists and the package imports:

    ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
    "$ROOT/.venv/bin/python" -c "import genesis" 2>/dev/null && echo INFRA_OK || echo INFRA_INCOMPLETE
    
  • Onboarding — has the system been configured? The marker is written at the end of onboarding (or by a completed bootstrap.sh):

    test -f ~/.genesis/setup-complete && echo ONBOARDED || echo NOT_ONBOARDED
    

Step 2 — Route (decide in this order)

  1. INFRA_INCOMPLETE — the install is broken or half-finished (e.g. an interrupted bootstrap.sh). Onboarding cannot run on a broken install, so repair the infrastructure first → Config repair below. After it completes, if keys/identity still need configuring, ask Genesis to "run onboarding" — the skill will run the sections you need.
  2. INFRA_OK + NOT_ONBOARDED — a complete install that has not been configured → Guided onboarding below. (Even if the user said "repair" — there is no configured system to repair yet; onboarding is the setup.)
  3. INFRA_OK + ONBOARDED — an already-configured install → Config repair below (the usual reason to run /setup on a working system).

Guided onboarding

Read src/genesis/skills/onboarding/SKILL.md and follow its steps: it configures the user profile, essential API keys, Telegram, GitHub backup, and verifies endpoints, then writes the ~/.genesis/setup-complete marker itself at the end. Do not run bootstrap.sh for onboarding — bootstrap is infrastructure setup, not the onboarding flow.

Read the full file on GitHub · 80 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. 1mo ago First seen · 80 lines · 61 tokens per session scan B 492276c937ec

Subscribe to this mod's changes

setup is a command published in the GitHub repository WingedGuardian/GENesis-AGI (99 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 844 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.