Animus Skills
The fastest way to turn Claude Code (or Codex, OpenCode, Cursor) into an autonomous engineering team that ships PRs while you sleep.
Animus is a Rust agent orchestrator. A daemon dispatches workflows from a queue, uses provider and subject plugins to run agents in isolated worktrees, runs your tests, opens PRs, and reviews them — on cron, on demand, or in response to events. animus-skills is the skill bundle that teaches your agent how to drive it.
You point a fresh agent at this README. It installs the CLI, links the skills, wires up MCP, and you start running workflows in about a minute.
Who this is for:
- Solo builders who want 5–15 parallel sprints running across their repos
- Small teams who need a self-hosted, auditable orchestrator (no cloud lock-in)
- Agent power users who already use Claude Code / Codex / Cursor and want a real backend
Quick start
- Install (30 seconds — see below)
cd into any repo and run /animus-setup — scaffolds .animus/, writes a first workflow, starts the daemon/animus-getting-started — creates your first task and runs it end-to-endanimus daemon stream — watch the agent work in real time- Stop here. If you can run a workflow on a real task, you'll know if Animus is for you.
Install — 30 seconds
Requirements: Claude Code (or Codex / OpenCode / Cursor), Git, bash, curl. Animus itself is a single Rust binary — no Node, no Python, no Docker.
One paste, any agent
Open a fresh Claude Code session and paste this. The agent does the rest — clones the repo, installs the animus CLI, links every skill into your host's skill directory, and writes .mcp.json if you're inside a project:
Install Animus + Animus Skills: run git clone --single-branch --depth 1 https://github.com/launchapp-dev/animus-skills.git ~/.claude/skills/animus-skills && cd ~/.claude/skills/animus-skills && ./setup, then add an "Animus" section to CLAUDE.md (or AGENTS.md for Codex) listing the available slash commands: /animus-setup, /animus-bootstrap, /animus-getting-started, /animus-mcp-setup, /animus-workflow-authoring, /animus-pack-authoring, /animus-skill-authoring, /animus-troubleshooting. Restart the agent so the new MCP server (animus) is picked up.
For Codex CLI, swap the clone path to ~/.codex/skills/animus-skills and AGENTS.md instead of CLAUDE.md.
Power user — explicit script
git clone https://github.com/launchapp-dev/animus-skills.git ~/animus-skills
cd ~/animus-skills && ./setup # auto-detects installed hosts
./setup --host claude # only Claude Code
./setup --host codex # only Codex
./setup --host all # every supported host (claude, codex, opencode, cursor, slate, kiro)
./setup --no-cli # skip the animus CLI install (use existing binary)
./setup --no-mcp # skip writing .mcp.json into the current project
The script:
- Installs the
animus CLI to ~/.local/bin/animus if it's not already on PATH.
- Symlinks each skill into the host's skill directory (e.g.
~/.claude/skills/<skill-name>, ~/.codex/skills/<skill-name>). Hosts discover skills flat as <host-skills-dir>/<name>/SKILL.md, so the script links one level down rather than the whole repo.
- Writes a project-local
.mcp.json exposing the animus MCP server (skipped if one already exists or you pass --no-mcp).
Claude Code marketplace (alternative)
/plugin marketplace add launchapp-dev/animus-skills
This skips the CLI install and MCP wiring — pair it with a manual curl -fsSL https://raw.githubusercontent.com/launchapp-dev/animus-cli/main/scripts/install.sh | bash if you don't already have animus.
See it work
You: /animus-setup
Claude: [scaffolds .animus/, writes config.json, generates a first workflow YAML,
starts the daemon, verifies MCP is reachable]
You: Create a task to add rate limiting to the /api/upload endpoint.
Claude: [calls animus.subject.create with kind=task, then enqueues TASK-001]
You: Run it.
Claude: [calls animus.workflow.run — daemon picks up TASK-001, spawns a
Claude session in an isolated worktree, runs the standard pipeline:
research → plan → implement → test → review → PR]
You: animus daemon stream
[live JSONL — phase transitions, model calls, test runs, git ops]
You: Now schedule a nightly retro across all my repos.
Claude: [edits .animus/workflows/retro.yaml, adds a cron schedule, restarts daemon]
Every step is replayable from the queue — pause, resume, drop, reorder, hold. Failed phases are sticky (the daemon won't silently retry and burn API credits). Outputs land in ~/.animus/<repo-scope>/runs/ so you can audit exactly what each model did.
Slash commands
