setup
Project setup jobs in one plugin. Investigates a repository and provisions it — plugins, tools, framework best-practice references, and a seeded knowledge base — then installs the adaptive statusline and indexes every skill reachable from the project into browsable markdown.
| Version | 1.0.0 |
| Marketplace | magus |
| Commands | 4 |
| Subagents | 0 |
| Skills | 2 |
| MCP server | no |
| Hooks | no |
What it's for
Three jobs that all happen when you arrive at a repository, or when you want it set up the same way as the last one.
| Job | Command |
|---|---|
| Work out what this repo is, and provision it | /setup:project |
| Put a statusline in Claude Code | /setup:statusline-install |
| List every skill you have, and what it costs you per turn | /setup:index-skills |
The statusline lives here
The statusline is part of setup. Enable setup@magus and you have it.
/setup:statusline-install project or global
/setup:statusline-customize sections, theme, bar widths
/setup:statusline-uninstall
It shows the worktree you're in, your plan limits, and the countdown to reset.
/setup:statusline-customize walks you through the options. It loads the configuration
reference itself, so there is nothing else for you to invoke.
Knowing what your skills cost
/setup:index-skills walks every skill reachable from the project — all plugins, all
marketplaces, plus your own — and writes a browsable index.
The useful part is the per-turn cost. Every skill's description is injected into every turn, out of a budget shared by everything you have installed. This is how you find out which plugin is eating it.
Install
claudeup
Find setup on the Plugins tab and turn it on. claudeup registers the magus
marketplace if you do not have it, and installs what the plugin needs to actually run —
binaries, MCP servers, CLI tools.
For a team, press s to save your plugins as a profile and commit it. Everyone else runs
claudeup install — see Teams and profiles.
Prefer to do it by hand? Installing Magus has the manual path.
Commands
| Command | What it does |
|---|---|
/setup:project | Investigate this repository and provision it — plugins, tools, MCP servers, framework references, and a seeded knowledge base |
/setup:statusline-customize | Interactively configure statusline sections, theme, and bar widths |
/setup:statusline-install | Install colorful statusline with worktree awareness, plan limits, and reset countdowns (project or global) |
/setup:statusline-uninstall | Remove the statusline from Claude Code (project or global) |
Skills
| How you get it | |
|---|---|
| ○ | You invoke it by name |
| ▸ | A command loads it for you — you never name it |
Why a skill lands in one row or another
| Skill | What it covers | |
|---|---|---|
| ○ | setup:index-skills | Walks every skill reachable from this project and writes a browsable markdown index, plus a small deterministic index spliced into CLAUDE.md. |
| ▸ | setup:statusline-customization | Configuration reference and troubleshooting for the statusline plugin — sections, themes, bar widths, and script architecture |
Source
plugins/setup/ on GitHub, including its full README.