aiblueprint-cli 1.1.7 → 1.2.0

package/README.md

@@ -7,6 +7,21 @@ A comprehensive CLI tool for supercharging Claude Code with security, productivi
 
 ## 🚀 Quick Start
 
+### Option 1: Install as Claude Code Plugin (Recommended)
+
+```bash
+# Add the AIBlueprint marketplace
+/plugin marketplace add melvynx/aiblueprint
+
+# Install the base plugin
+/plugin install aibp-base@AIBlueprint
+
+# Or install directly from GitHub
+/plugin install github:melvynx/aiblueprint
+```
+
+### Option 2: Use the CLI Tool
+
 ```bash
 # Run immediately without installation
 bunx aiblueprint-cli@latest claude-code setup
@@ -18,7 +33,8 @@ aiblueprint claude-code setup
 
 ## 📋 Table of Contents
 
-- [Installation & Usage](#installation--usage)
+- [Plugin Installation](#-plugin-installation)
+- [CLI Installation & Usage](#-cli-installation--usage)
 - [Command Reference](#command-reference)
 - [Available Features](#available-features)
 - [Configuration System](#configuration-system)
@@ -27,7 +43,63 @@ aiblueprint claude-code setup
 - [Security Features](#security-features)
 - [Development](#development)
 
-## 💾 Installation & Usage
+## 🔌 Plugin Installation
+
+### Install from Claude Code Plugin Marketplace
+
+The easiest way to get started is by installing AIBlueprint as a Claude Code plugin:
+
+```bash
+# Step 1: Add the AIBlueprint marketplace
+/plugin marketplace add melvynx/aiblueprint
+
+# Step 2: Install the aibp-base plugin
+/plugin install aibp-base@AIBlueprint
+
+# Alternative: Install directly from GitHub
+/plugin install github:melvynx/aiblueprint
+```
+
+### What Gets Installed
+
+The `aibp-base` plugin includes:
+- ✅ **16 Custom Commands** - `/commit`, `/create-pull-request`, `/deep-code-analysis`, etc.
+- ✅ **3 Specialized Agents** - explore-codebase, Snipper, websearch
+- ✅ **Security Hooks** - Command validation and TypeScript processing
+- ✅ **Custom Statusline** - Git status, cost tracking, and token usage
+- ✅ **Notification Sounds** - Audio alerts for task completion
+
+### Plugin Management
+
+```bash
+# List installed plugins
+/plugin list
+
+# Update plugin to latest version
+/plugin update aibp-base
+
+# Remove plugin
+/plugin uninstall aibp-base
+
+# View marketplace plugins
+/plugin marketplace list
+```
+
+### Plugin vs CLI Tool
+
+**Plugin Installation (Recommended)**:
+- ✅ Automatic updates via marketplace
+- ✅ No CLI tool installation needed
+- ✅ Direct integration with Claude Code
+- ✅ Easy to manage and update
+
+**CLI Tool Installation**:
+- ✅ More control over installation
+- ✅ Custom folder locations
+- ✅ Interactive feature selection
+- ✅ Symlink management for other tools
+
+## 💾 CLI Installation & Usage
 
 ### Installation Methods
 
@@ -67,6 +139,7 @@ bunx aiblueprint-cli@latest claude-code setup  # Creates .claude/ in project roo
 |---------|-------------|---------|
 | `bunx aiblueprint-cli@latest claude-code setup` | Interactive setup with feature selection | `-f, --folder <path>` (alias for --claudeCodeFolder), `--claudeCodeFolder <path>`, `--codexFolder <path>`, `--openCodeFolder <path>`, `--factoryAiFolder <path>`, `-s, --skip` |
 | `bunx aiblueprint-cli@latest claude-code symlink` | Create symlinks between CLI tools (Codex, OpenCode, FactoryAI) | `--claudeCodeFolder <path>`, `--codexFolder <path>`, `--openCodeFolder <path>`, `--factoryAiFolder <path>` |
+| `bunx aiblueprint-cli@latest claude-code statusline` | Setup custom statusline with git status, costs, and token usage | `-f, --folder <path>` |
 | `bunx aiblueprint-cli@latest claude-code add hook <type>` | Install specific hook | `-f, --folder <path>` |
 | `bunx aiblueprint-cli@latest claude-code add commands [name]` | List or install commands | `-f, --folder <path>` |
 
@@ -89,6 +162,10 @@ bunx aiblueprint-cli@latest claude-code add commands deep-code-analysis # Instal
 # Create symlinks between CLI tools
 bunx aiblueprint-cli@latest claude-code symlink                         # Interactive symlink manager
 bunx aiblueprint-cli@latest claude-code symlink --factoryAiFolder ~/.factory  # With custom paths
+
+# Setup statusline
+bunx aiblueprint-cli@latest claude-code statusline                      # Quick statusline setup
+bunx aiblueprint-cli@latest claude-code statusline --folder ~/.my-claude # Custom location
 ```
 
 ### Hook Types Available
@@ -121,6 +198,7 @@ The CLI intelligently determines where to install configurations:
 - **Cost tracking** - Session costs, daily limits, and token usage via ccusage
 - **Real-time updates** - Command-triggered statusline refresh
 - **Colored output** - Visual indicators for different status types
+- **Quick setup** - Install with one command: `pnpm dlx aiblueprint-cli claude-code statusline`
 
 ### 🤖 AIBlueprint Commands (16 Available)
 
@@ -147,12 +225,6 @@ The CLI intelligently determines where to install configurations:
 - **Snipper** (blue) - Rapid code modification specialist with minimal output
 - **websearch** (yellow) - Quick web research with authoritative sources
 
-### 🎨 Output Styles (3 Personalities)
-
-- **Assistant** - Professional "Bob" persona with honest, task-focused communication
-- **senior-dev** - Casual engineering teammate style, direct and conversational
-- **Honest Friend** - WhatsApp-style brutally honest feedback from a successful friend
-
 ### 🔊 Notification Sounds
 - **Finish sound** - Audio alert for completed operations (macOS afplay)
 - **Need-human sound** - Audio alert for attention requests
@@ -179,7 +251,7 @@ The CLI automatically manages your `~/.claude/settings.json` with:
 {
   "statusLine": {
     "type": "command",
-    "command": "bash ~/.claude/scripts/statusline-ccusage.sh",
+    "command": "bun ~/.claude/scripts/statusline/src/index.ts",
     "padding": 0
   },
   "hooks": {
@@ -397,7 +469,6 @@ claude-code-config/                 # Template repository
 ├── hooks/                          # Hook scripts
 ├── agents/                         # Agent configurations
 ├── scripts/                        # Utility scripts
-├── output-styles/                  # Style templates
 └── song/                           # Notification sounds
 ```
 
@@ -454,4 +525,4 @@ MIT License - see [LICENSE](LICENSE) file for details.
 
 **Created by AIBlueprint** - Enhancing Claude Code for modern development workflows.
 
-Need help? [Open an issue](https://github.com/aiblueprint/aiblueprint-cli/issues) or check our [documentation](https://docs.aiblueprint.dev).
+Need help? [Open an issue](https://github.com/melvynx/aiblueprint/issues) or check our [documentation](https://docs.aiblueprint.dev).

package/claude-code-config/agents/action.md

@@ -0,0 +1,36 @@
+---
+name: action
+description: Conditional action executor - performs actions only when specific conditions are met
+color: purple
+model: haiku
+---
+
+Batch conditional executor. Handle ≤5 tasks. VERIFY INDEPENDENTLY before each action.
+
+## Workflow
+
+1. **VERIFY each item yourself** (never trust input):
+   - **Exports/Types**: Grep for `import.*{name}` in codebase
+   - **Files**: Check framework patterns via explore-docs, then Grep for imports
+   - **Dependencies**: Grep for `from 'pkg'` or `require('pkg')`
+
+2. **Execute ONLY if verified unused**:
+   - If used → Skip with reason, continue next
+   - If unused → Execute action, confirm success
+
+3. **Report**: Count executed, count skipped with reasons
+
+## Rules
+
+- **MANDATORY**: Verify each item independently using Grep/explore-docs
+- **Skip if used**: Continue to next task
+- **Max 5 tasks**: Process all in batch
+
+## Example
+
+"Verify and remove: lodash, axios, moment"
+
+1. Grep `lodash` → Found in utils.ts → Skip
+2. Grep `axios` → Not found → `pnpm remove axios` → Done
+3. Grep `moment` → Not found → `pnpm remove moment` → Done
+   Report: "Removed 2/3: axios, moment. Skipped: lodash (used in utils.ts)"

package/claude-code-config/agents/explore-codebase.md

@@ -2,7 +2,7 @@
 name: explore-codebase
 description: Use this agent whenever you need to explore the codebase to realize a feature.
 color: yellow
-model: sonnet
+model: haiku
 ---
 
 You are a codebase exploration specialist. Your only job is to find and present ALL relevant code and logic for the requested feature.
@@ -56,3 +56,8 @@ Related to: [How it connects to the feature]
 - External services to research: [list]
 
 Focus on discovering and documenting existing code. Be thorough - include everything that might be relevant.
+
+## Exa MCP
+
+- You can use Exa web search for quick search
+- Avoid using it too much, maximum 2-3 calls and then use WebSearch. Each call cost 0.05$

package/claude-code-config/agents/explore-docs.md

@@ -2,7 +2,7 @@
 name: explore-docs
 description: Use this agent IMMEDIATELY when the user asks about library features, implementation methods, "how to do X with Y library", documentation searches, or ANY question about using/implementing specific libraries or frameworks (in any language) - launches Context7 and WebFetch for precise technical information with code examples
 color: yellow
-model: sonnet
+model: haiku
 ---
 
 You are a documentation exploration specialist. Your mission is to retrieve precise, actionable documentation with code examples while eliminating superficial content.

package/claude-code-config/agents/websearch.md

@@ -3,7 +3,7 @@ name: websearch
 description: Use this agent when you need to make a quick web search.
 color: yellow
 tools: WebSearch, WebFetch
-model: sonnet
+model: haiku
 ---
 
 You are a rapid web search specialist. Find accurate information fast.

package/claude-code-config/commands/commit.md

@@ -14,7 +14,7 @@ You are a git commit automation tool. Create minimal, clean commits for a tidy g
    - `feat: [what was added]`
    - `update: [what was modified]`
    - `refactor: [what was reorganized]`
-4. **Push**: `git push` immediately
+4. **Push**: `git push` immediatelyne
 
 ## Message Rules
 

package/claude-code-config/commands/oneshot.md

@@ -0,0 +1,57 @@
+---
+description: Ultra-fast feature implementation - Explore then Code then Test
+argument-hint: <feature-description>
+---
+
+You are a rapid implementation specialist. Implement features at maximum speed using the OneShot methodology.
+
+**You need to always ULTRA THINK.**
+
+## Workflow
+
+1. **EXPLORE**: Quick context gathering (5-10 minutes max)
+   - Launch **1-2 parallel subagents maximum** to find relevant files
+   - Prefer `explore-codebase` agent for codebase search
+   - Use `explore-docs` agent ONLY if library-specific knowledge needed
+   - Find files to use as **examples** or **edit targets**
+   - **CRITICAL**: Be surgical - know exactly what to search for
+   - **NO PLANNING PHASE** - gather context and move directly to coding
+
+2. **CODE**: Implement immediately following existing patterns
+   - Start coding as soon as you have basic context
+   - Follow existing codebase style:
+     - Prefer clear variable/method names over comments
+     - Match existing patterns and conventions
+   - **CRITICAL RULES**:
+     - Stay **STRICTLY IN SCOPE** - change only what's needed
+     - NO comments unless absolutely necessary
+     - NO refactoring beyond the feature requirements
+   - Run autoformatting scripts when done
+   - Fix reasonable linter warnings as you go
+
+3. **TEST**: Validate with ESLint and TypeScript
+   - **First check package.json** for available scripts:
+     - Look for: `lint`, `typecheck`, `format`
+     - Run: `npm run lint && npm run typecheck` (or equivalent)
+   - **CRITICAL**: Code must pass linting and type checks
+   - If checks fail: fix errors immediately and re-run
+   - **STAY IN SCOPE**: Don't run full test suite unless explicitly requested
+   - For major changes only: run relevant tests with `npm test -- <pattern>`
+
+## Execution Rules
+
+- **SPEED IS PRIORITY**: Move fast, break nothing
+- **NO PLANNING**: Trust your exploration and code directly
+- **PARALLEL AGENTS**: Max 2 agents during explore phase
+- **MINIMAL TESTS**: Lint + typecheck only (unless user requests more)
+- **STAY FOCUSED**: Implement exactly what's requested, nothing more
+- Never exceed task boundaries
+- If stuck or uncertain: ask user immediately instead of over-exploring
+
+## Priority
+
+Speed > Completeness. Ship fast, iterate later.
+
+---
+
+User: $ARGUMENTS

package/claude-code-config/hooks/hooks.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bun ${CLAUDE_PLUGIN_ROOT}/claude-code-config/scripts/validate-command.js"
+          }
+        ]
+      }
+    ]
+  }
+}

package/claude-code-config/scripts/command-validator/README.md

@@ -0,0 +1,147 @@
+# Command Validator
+
+A secure command validation package for Claude Code's PreToolUse hook. This package validates bash commands before execution to prevent dangerous operations.
+
+## Features
+
+- **Comprehensive Security Rules**: Blocks dangerous commands (rm -rf /, dd, mkfs, etc.)
+- **Pattern Matching**: Detects malicious patterns like fork bombs, backdoors, and data exfiltration
+- **Path Protection**: Prevents writes to system directories (/etc, /usr, /bin, etc.)
+- **Command Chaining**: Validates chained commands (&&, ||, ;)
+- **Fully Tested**: 82+ tests with Vitest ensuring reliable validation
+
+## Installation
+
+```bash
+bun install
+```
+
+## Usage
+
+### As a Claude Code Hook
+
+The validator is configured as a PreToolUse hook in Claude Code settings:
+
+```json
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bun /Users/melvynx/.claude/scripts/command-validator/src/cli.ts"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Programmatic Usage
+
+```typescript
+import { CommandValidator } from "./src/lib/validator";
+
+const validator = new CommandValidator();
+const result = validator.validate("rm -rf /");
+
+if (!result.isValid) {
+  console.log(`Blocked: ${result.violations.join(", ")}`);
+  console.log(`Severity: ${result.severity}`);
+}
+```
+
+## Testing
+
+```bash
+# Run all tests
+bun test
+
+# Run tests with UI
+bun test:ui
+```
+
+## Test Coverage
+
+The test suite includes:
+
+### Safe Commands (Must Allow)
+- Standard utilities: ls, git, npm, pnpm, node, python
+- File operations: cat, cp, mv, mkdir, touch
+- Safe command chains with &&
+
+### Dangerous Commands (Must Block)
+- System destruction: rm -rf /, dd, mkfs, fdisk
+- Privilege escalation: sudo, chmod, chown, passwd
+- Network attacks: nc, nmap, telnet
+- Malicious patterns: fork bombs, backdoors, log manipulation
+- Sensitive file access: /etc/passwd, /etc/shadow, /etc/sudoers
+
+### Special Cases
+- rm -rf safety: Allows deletions in safe paths (/Users/melvynx/Developer/, /tmp/)
+- Protected paths: Blocks dangerous operations on /etc, /usr, /bin, etc.
+- Binary content detection
+- Command length limits
+
+## Architecture
+
+```
+src/
+├── cli.ts                 # CLI entry point (used by Claude Code hook)
+├── lib/
+│   ├── types.ts           # TypeScript interfaces
+│   ├── security-rules.ts  # Security rules database
+│   └── validator.ts       # Core validation logic
+└── __tests__/
+    └── validator.test.ts  # Comprehensive test suite
+```
+
+## Security Rules
+
+### Critical Commands
+- `del`, `format`, `mkfs`, `shred`, `dd`, `fdisk`, `parted`
+
+### Privilege Escalation
+- `sudo`, `su`, `passwd`, `chpasswd`, `usermod`, `chmod`, `chown`
+
+### Network Commands
+- `nc`, `netcat`, `nmap`, `telnet`, `ssh-keygen`, `iptables`
+
+### System Manipulation
+- `systemctl`, `service`, `kill`, `killall`, `mount`, `umount`
+
+### Protected Paths
+- `/etc/`, `/usr/`, `/sbin/`, `/boot/`, `/sys/`, `/proc/`, `/dev/`, `/root/`
+
+## Security Logs
+
+Security events are logged to `data/security.log` inside the package directory. The log file contains:
+- Timestamp
+- Session ID
+- Tool name
+- Command (truncated to 500 chars)
+- Blocked/allowed status
+- Severity level
+- Violations detected
+
+The `data/` folder is gitignored to prevent committing sensitive log data.
+
+## Development
+
+```bash
+# Run linter
+bun run lint
+
+# Format code
+bun run format
+
+# Type check
+bunx tsc --noEmit
+```
+
+## License
+
+MIT

package/claude-code-config/scripts/command-validator/biome.json

@@ -0,0 +1,29 @@
+{
+	"$schema": "https://biomejs.dev/schemas/2.3.4/schema.json",
+	"vcs": {
+		"enabled": false,
+		"clientKind": "git",
+		"useIgnoreFile": false
+	},
+	"files": {
+		"ignoreUnknown": false
+	},
+	"formatter": {
+		"enabled": true,
+		"indentStyle": "tab"
+	},
+	"linter": {
+		"enabled": true,
+		"rules": {
+			"recommended": true,
+			"suspicious": {
+				"noControlCharactersInRegex": "off"
+			}
+		}
+	},
+	"javascript": {
+		"formatter": {
+			"quoteStyle": "double"
+		}
+	}
+}