
Configure
The install command gets the plugin loaded, but this is what actually makes it enforce anything. It walks you through bootstrapping the contract library tree, installing pre-built rule sets for common MCP servers like github and filesystem (blocks on deleting main branches, .env files, that kind of thing), and running scan to generate starter rules for anything custom you've wired up. The bundled libraries are opinionated, they ship real denies out of the box, and the digest output shows you exactly what just got armed before you flip to enforce mode. If you're running Sponsio as a Claude Code host plugin rather than wiring it into your own agent framework, this is the second half of setup you can't skip.
- GitHub stars
- 476
- last updated
- Jun 10, 2026
Install
$ npx -y skills add sponsiolabs/sponsio --skill configure --agent claude-codeInstalls into .claude/skills of the current project.
Files
sponsio-claude-code — configure the host shield
You are walking the user through configuring the sponsio-claude-code plugin so it actually wraps tool calls in this Claude Code session. Without these steps, the plugin loads but every per-plugin library is empty and every tool call passes through unguarded.
The flow has two halves: setup (steps 1–2, 4–6) covers the common case where the user runs popular MCP servers we ship starters for; scan (step 3) covers plugins / MCP servers without a bundled starter and lives inline because most sessions touch both halves.
Prerequisites (check silently first)
Run:
sponsio --version
- Not found → tell the user to install:
pip install sponsio(orpip install -e ".[all]"from a local clone). Stop here until they confirm. - Present → continue.
Sponsors
Details
- Repository
- github.com/sponsiolabs/sponsio
- Categories
- Frontend Development, Backend & APIs, Testing & QA, Git & Pull Requests, AI & Agent Building, Release Management
- License
- Apache-2.0
- First seen
- Jun 11, 2026