karukia-mcp 1.2.0 → 1.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +11 -9
  2. package/dist/http.js +104 -103
  3. package/dist/index.js +104 -103
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -58,19 +58,21 @@ Restart Claude Code (`/quit` then relaunch) or your IDE. The 21 KARUKIA tools ar
58
58
 
59
59
  Tell your AI:
60
60
 
61
- > "Call the `install` tool from karukia"
61
+ > "karukia install"
62
62
 
63
63
  KARUKIA scans your project, detects your stack, and generates configuration files (security scope, CLAUDE.md, memory structure).
64
64
 
65
65
  ### Step 4 — Start working
66
66
 
67
- > "Use /auto to add user authentication"
68
- > "Use /auto to audit security"
69
- > "Use /auto to run a pentest"
67
+ Just describe what you need in natural language:
70
68
 
71
- `/auto` is your daily driver. It routes your request to the right specialists automatically.
69
+ > "karukia: add user authentication"
70
+ > "karukia: audit security"
71
+ > "karukia: run a pentest"
72
72
 
73
- > **Tip:** You only need two tools: `/install` (once) then `/auto` (always). For direct control, call `/neo`, `/viper`, or `/jeffrey` individually. Call `start` anytime for a full guide.
73
+ The orchestrator (`auto`) analyzes your request and routes to the right specialists automatically.
74
+
75
+ > **Tip:** You only need two commands: `karukia install` (once) then `karukia` + your request (always). For direct control, ask for a specific skill: "karukia neo", "karukia viper", "karukia jeffrey". Say "karukia start" anytime for a full guide.
74
76
 
75
77
  ### Where to put the config
76
78
 
@@ -193,19 +195,19 @@ Your AI calls `neo` — becomes the Neo security auditor — follows the methodo
193
195
 
194
196
  ### Build a feature with guardrails
195
197
 
196
- > "Implement user authentication with /jeffrey"
198
+ > "karukia jeffrey: implement user authentication"
197
199
 
198
200
  Your AI calls `jeffrey` — becomes the Jeffrey architect — implements with TDD, then chains to Neo for security validation (rejection loop: if Neo rejects, Jeffrey fixes, max 3 iterations).
199
201
 
200
202
  ### Pentest your app
201
203
 
202
- > "Run a pentest with /viper"
204
+ > "karukia viper"
203
205
 
204
206
  Your AI calls `viper` — deploys the Brigade methodology with 16 specialized agents across Recon, Surface Analysis, and Exploitation phases.
205
207
 
206
208
  ### Orchestrate everything
207
209
 
208
- > "Use /auto to handle my request"
210
+ > "karukia: add a logout button and audit security"
209
211
 
210
212
  Your AI calls `auto` — analyzes the request — routes to the right skill(s) — manages the chain.
211
213