
Security News
Feross on TBPN: How North Korea Hijacked Axios
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.
claude-power-setup
Advanced tools
Multi-agent orchestration, automation pipelines, and self-improvement for Claude Code
Multi-agent orchestration, automation pipelines, and recursive self-improvement for Claude Code.
Layers on top of ECC (Everything Claude Code). One command to install:
npm install -g claude-power-setup
claude-power-setup
Claude Code is powerful out of the box, but using it at maximum efficiency requires expertise most developers don't have time to build. You end up with:
This setup is built on three beliefs about AI-assisted development:
1. Mode switching is not optional — it's fundamental.
A developer reviewing code should think differently than a developer writing code. When you're in research mode, you should be read-only and methodical. When you're orchestrating a team, you should decompose and delegate, not implement. Claude Code doesn't enforce this separation. We do — with four purpose-built context profiles that prime the agent for the task at hand.
2. The agent should get smarter over time, not just the developer.
Most AI coding tools are stateless. They make the same mistakes on day 100 that they made on day 1. The Continuous Learning system changes this: every tool use is observed, patterns are detected, instincts are created with confidence scores, and high-confidence instincts are promoted from project-scoped to global. Your Claude gets better at your codebases, with your preferences, automatically.
3. Orchestration beats implementation.
The highest-leverage thing a developer can do with AI agents is not write code through them — it's orchestrate multiple agents in parallel. One agent researches. Another implements. A third writes tests. A fourth reviews. They work in isolated worktrees with independent context windows, communicate through a shared task board, and produce work that no single agent session could match. This is swarm engineering, and it's the default mode for complex tasks.
This isn't a collection of dotfiles or a prompt library. It's an operating system layer for Claude Code:
cpipeline, crouted, claude-loop) replace manual multi-step workflows with deterministic, quality-gated sequencesThe result: you spend less time managing the AI and more time thinking about the problem.
| Requirement | Required | Notes |
|---|---|---|
| Node.js 18+ | Yes | Hooks and scripts depend on it |
| Claude Code CLI | Yes | npm install -g @anthropic-ai/claude-code |
| Git | Recommended | Worktrees, session save, loop runner |
| ECC | Recommended | This setup extends ECC's hooks and skills |
npm install -g claude-power-setup
claude-power-setup
git clone https://github.com/shyamsridhar123/claude-power-setup.git
cd claude-power-setup
bash install.sh
git clone https://github.com/shyamsridhar123/claude-power-setup.git
cd claude-power-setup
powershell -ExecutionPolicy Bypass -File install.ps1
--dry-run Show what would be installed without writing files
--force Overwrite existing files instead of skipping
--skip-shell Don't modify shell profile (.bashrc/.zshrc)
--skip-ecc Don't check for ECC installation
Switch between purpose-built Claude modes. Each profile primes the agent with different priorities, allowed tools, and quality gates:
source ~/.claude/bin/claude-aliases.sh
cdev # Development mode — TDD, quality gates, strategic compaction
corchestrate # Team lead mode — decompose, delegate, synthesize
creview # Code review mode — security-first, dual-model review
cresearch # Research mode — read-only investigation, document findings
Replace multi-step manual workflows with deterministic, scriptable pipelines:
# Sequential: implement -> de-slop -> verify -> commit
cpipeline "Implement OAuth2 login in src/auth/"
# Model-routed: Opus research -> Sonnet implement -> Opus review
crouted "Add caching layer to API endpoints"
# Continuous loop with safety controls
~/.claude/bin/claude-loop.sh "Add tests for untested functions" --max-runs 8
# Quick commands
cfix # Build + lint + test + fix failures
cclean # Remove slop from uncommitted changes
ccommit # Auto-commit with conventional message
caudit # Security scan + harness audit
Enabled via CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Just ask naturally:
> Build a REST API with auth, rate limiting, and tests.
> Please use a team of specialists for this.
Claude spawns teammates in isolated worktrees — each with fresh context, self-organizing via a shared task board. Up to 5 specialists working in parallel: architect, backend, frontend, tester, reviewer, docs.
Four battle-tested patterns extracted from real development sessions. These load automatically and improve agent behavior without prompt engineering:
| Instinct | Confidence | What It Does |
|---|---|---|
| Parallel agents for independent files | 0.8 | Spawn parallel agents when 3+ files don't depend on each other |
| De-sloppify as separate pass | 0.85 | Always clean up with a different agent than the one that wrote the code |
| Dual-review catches more | 0.9 | Two independent reviewers find ~45% more issues than one |
| uuid ESM incompatibility | 0.95 | Use crypto.randomUUID() instead of uuid package in Jest/CJS projects |
The system watches every tool use, detects patterns in your workflow, and creates new instincts automatically:
Observe (every tool use) -> Detect (patterns emerge) -> Learn (create instincts)
-> Promote (project -> global) -> Evolve (instincts -> skills/agents)
Instincts have confidence scores (0.3 tentative to 0.95 certain) that evolve as evidence accumulates. High-confidence instincts are promoted from project scope to global scope automatically.
YOU (developer)
|
+-- Mode Selection: cdev | corchestrate | creview | cresearch
|
+-- Orchestration: Agent Teams | Swarm Mode | Santa Loop | Multi-Model
|
+-- Loop Engine: Sequential Pipeline | Continuous Loop | Model-Routed
|
+-- Quality Layer: TDD Guide | Verify Loop | De-Slop Pass
|
+-- Memory & Learning: Session Save/Resume | Instincts (v2.1) | Strategic Compact
|
+-- Security & Hooks: PreToolUse | PostToolUse | Stop/Session hooks
See ~/.claude/contexts/ORCHESTRATION-REFERENCE.md for the full reference with architecture diagrams, decision matrices, and workflow examples.
claude-power-setup/
├── install.sh # Main installer (bash, cross-platform)
├── install.ps1 # Windows PowerShell wrapper
├── uninstall.sh # Safe removal (only touches what it installed)
├── cli.js # npm entry point (npx claude-power-setup)
├── package.json # npm package config
├── README.md # This file
├── LICENSE # MIT
├── assets/ # README assets
│ └── banner.svg # Terminal-style banner in Anthropic colors
├── contexts/ # Mode profiles
│ ├── dev.md
│ ├── orchestrate.md
│ ├── review.md
│ └── research.md
├── bin/ # Automation scripts
│ ├── claude-aliases.sh # Mode aliases + pipeline functions
│ ├── claude-loop.sh # Continuous loop with quality gates
│ └── claude-session-save.sh # Cross-session memory persistence
├── instincts/ # Learned patterns with confidence scores
│ ├── parallel-agents-for-independent-files.md
│ ├── de-sloppify-separate-pass.md
│ ├── dual-review-catches-more.md
│ └── uuid-esm-incompatibility-jest.md
├── config/ # Settings templates
│ ├── env-settings.json # Agent Teams, cost tracking, hook profile
│ └── observer-config.json # Continuous learning observer config
├── reference/ # Documentation
│ └── ORCHESTRATION-REFERENCE.md
└── video/ # Remotion source for feature video
├── index.ts
├── Root.tsx
└── scenes/
└── FeatureVideo.tsx
bash uninstall.sh # Interactive removal
bash uninstall.sh --dry-run # Preview what would be removed
The uninstaller only removes files it installed. It never touches ECC hooks, plugins, session data, user-created instincts, or user-modified settings. Env settings are only reverted if their values still match what was installed (user modifications are preserved).
After installation, these slash commands become available in Claude Code:
| Command | Purpose |
|---|---|
/plan | Plan before coding (wait for confirmation) |
/tdd | Test-driven development workflow |
/verify | Full verification loop (build + lint + test + security) |
/code-review | Comprehensive quality review |
/santa-loop | Dual-model adversarial review (both must approve) |
/team-builder | Compose and dispatch agent teams |
/learn | Extract reusable patterns from current session |
/instinct-status | View all learned instincts with confidence |
/save-session | Persist session state for later resumption |
/resume-session | Load previous session and continue |
/promote | Move project instincts to global scope |
/evolve | Cluster instincts into skills/agents |
/security-scan | Scan configuration for vulnerabilities |
Contributions welcome. If you've discovered patterns that make Claude Code more effective, consider adding them as instincts with evidence and confidence scores.
FAQs
Multi-agent orchestration, automation pipelines, and self-improvement for Claude Code
We found that claude-power-setup demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.

Security News
OpenSSF has issued a high-severity advisory warning open source developers of an active Slack-based campaign using impersonation to deliver malware.

Research
/Security News
Malicious packages published to npm, PyPI, Go Modules, crates.io, and Packagist impersonate developer tooling to fetch staged malware, steal credentials and wallets, and enable remote access.