Zookanalytics Claude Devcontainer
zookanalytics-claude-devcontainer is a Claude Code plugin bundle for the Build phase that delivers a firewall-aware devcontainer and orchestration hooks for secure agent development.
by zookanalytics · github.com/zookanalytics/claude-devcontainer
Run Claude Code inside a secure, firewall-aware devcontainer with orchestration, git hooks, and session tracking for consistent multi-instance development.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install zookanalytics-claude-devcontainer@zookanalytics/claude-devcontainerBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:zookanalytics/claude-devcontainer") and the paste-ready config with skillselion.get_install_config("plugin:zookanalytics/claude-devcontainer").
What it does
zookanalytics-claude-devcontainer packages a security-minded development environment for Claude Code: an opinionated devcontainer image with firewall allowlisting plus three plugins that touch orchestration, git enforcement, and session-oriented workflow tracking. Indie builders and small analytics teams use it when local setups leak too much network access, when multiple Claude instances need coordinated management, or when commits should pass hook-based checks before they land. Keywords reference BMAD workflows, multi-instance orchestrators, skills, and review tracking—positioning this as infrastructure for agentic development, not a single feature skill. Setup is intermediate: Docker or devcontainer familiarity, allowlist tuning, and hook configuration matter. It is weaker as a choice if you only code on host OS with no containers, or if you need a hosted SaaS IDE instead of a reproducible local image.
Highlights
- Three-plugin bundle atop a secure Claude Code-ready devcontainer base image
- Firewall domain allowlisting for controlled outbound access during agent work
- Multi-instance orchestration and session tracking for parallel agent workflows
- Git commit enforcement hooks and AI-driven review-oriented workflow support
- BMAD-style purpose-built orchestration keywords alongside skills and development hooks
Why builders use it
Ad-hoc Claude Code environments expose too much network access, lack repeatable tooling, and make multi-session agent work hard to track and enforce at commit time.
After setup, you develop inside an allowlisted devcontainer with orchestration, git enforcement, and session tracking aligned to Claude Code workflows.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is zookanalytics-claude-devcontainer for?
Solo builders and small teams, especially analytics-oriented shops, who standardize Claude Code in devcontainers with firewall rules and multi-instance workflow control.
When should I use zookanalytics-claude-devcontainer?
Use it when starting or hardening a Claude Code workspace where outbound domains must be allowlisted, git commits need enforcement, or several agent sessions need orchestration.
How do I add zookanalytics-claude-devcontainer to my agent?
Build or pull the zookanalytics/claude-devcontainer image, open the project in a devcontainer-capable editor, register the three plugins in Claude Code, and configure firewall allowlists and git hooks per repository documentation.
Comments
Share how you use zookanalytics-claude-devcontainer, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.