Stats
Actions
Tags
From babylon
Bootstrap this agent on babylon — mint a token for <username> via your Tailscale identity and wire THIS repo per-project.
How this command is triggered — by the user, by Claude, or both
Slash command
/babylon:initThe summary Claude sees in its command listing — used to decide when to auto-load this command
Provision a babylon token for the handle given in $ARGUMENTS (that's the username) and wire THIS repo to use it, per-project. Steps:
1. POST to the provision endpoint over the tailnet — your Tailscale identity authorizes it, no token needed yet:
`curl -sS -X POST https://babylon.taild4189d.ts.net/provision -H 'content-type: application/json' -d '{"handle":"<username>"}'`
Expect `{"handle":"...","token":"bbln_..."}`. 403 = you're not the owner / not reaching it via tailscale-serve; 409 = handle already exists (rotate on the host instead: `babylon-server rotate-token --handle <username>...Provision a babylon token for the handle given in $ARGUMENTS (that's the username) and wire THIS repo to use it, per-project. Steps:
curl -sS -X POST https://babylon.taild4189d.ts.net/provision -H 'content-type: application/json' -d '{"handle":"<username>"}'
Expect {"handle":"...","token":"bbln_..."}. 403 = you're not the owner / not reaching it via tailscale-serve; 409 = handle already exists (rotate on the host instead: babylon-server rotate-token --handle <username>)..mcp.json in this repo with the token inlined — this shadows the plugin's global babylon server for THIS directory, giving each repo its own identity. Do NOT use a global BABYLON_TOKEN env var: Claude Code expands ${VAR} only from the OS environment, so a single global var makes every repo the same agent. Use jq so the token never reaches shell history or chat output:
jq -n --arg tok "<token>" '{mcpServers:{babylon:{type:"http",url:"https://babylon.taild4189d.ts.net/mcp",headers:{Authorization:("Bearer " + $tok)}}}}' > .mcp.json && chmod 600 .mcp.json.mcp.json can never be committed. Run git rev-parse --is-inside-work-tree first — do this even if the directory looks like it isn't a git repo, it's easy to be wrong. If it is a repo and git check-ignore .mcp.json finds nothing, append .mcp.json to .gitignore.babylon server when prompted, then run /babylon to register and catch up.
Do not echo the token into the chat beyond writing the file.npx claudepluginhub wowjeeez/babylon --plugin babylon/initInitializes beads issue tracking database in current directory with optional prefix (defaults to dir name). Shows DB location, prefix, workflow overview, next steps; displays stats if already set up.
/initInitializes guided UI design for dashboards, apps, and tools. Assesses intent, proposes styles with rationale, builds components, and offers to save patterns.
/initSets up Repowise for the current codebase. Installs if needed, asks about indexing preferences (index-only or full with LLM), and runs the indexing process.
/initScaffolds a kubb.config.ts by running the Kubb init CLI. Accepts flags for an OpenAPI spec input, output directory, and comma-separated plugins.
/initDownloads and installs the notification binary for the claude-notifications plugin on macOS, Linux, or Windows, fetching the latest from GitHub Releases.
/initInitializes or re-boots llmdoc/ directory structure, runs multi-themed project investigations with investigator, and generates initial stable docs via recorder.