monomind 1.18.15 → 1.19.0

package/.claude/skills/mastermind-skills/architect.md

@@ -251,22 +251,21 @@ _entry=${_entry:-.}
   npx --yes madge --circular "$_entry/" 2>/dev/null; } | head -20
 
 # 6. Find god files (imported by many others)
-# NOTE: This step covers JS/TS/Vue and Python only.
-# For Go, Rust, Java, and other stacks, use mcp__monomind__monograph_god_nodes instead.
-# JS/TS/Vue: skip comment lines; perl extracts module name from from '...' or from "..."
-# --exclude-dir applied at grep level so exclusions work before -h strips filenames
+# PREFERRED: use monograph (pre-computed graph index, faster and more accurate)
+# Call mcp__monomind__monograph_god_nodes({}) first.
+# Only fall back to grep below if monograph returns 0 results or the DB is not built.
+#
+# FALLBACK (grep-based, JS/TS/Vue and Python only):
 grep -rh "^[^/]*from ['\"]" . \
   --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.vue" \
   --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=.git \
   2>/dev/null \
   | perl -ne 'if (/from\s+['"'"'"]([^'"'"'"\s]+)['"'"'"]/) { print "$1\n" }' \
   | sort | uniq -c | sort -rn | head -20
-# Python: count imports separately (no quotes in Python import syntax)
 grep -rh "^from \|^import " . --include="*.py" \
   --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=.git \
   2>/dev/null \
   | awk '{print $2}' | sed 's/,.*//' | sed 's/\..*//' | grep -v '^$' | sort | uniq -c | sort -rn | head -20
-# Note: if monograph is built, prefer mcp__monomind__monograph_god_nodes — it uses the pre-computed graph index
 ```
 
 For each finding, produce a **Deduplication Action Table**:

package/.claude/skills/mastermind-skills/autodev.md

@@ -48,19 +48,22 @@ Default `count = 1`.
 
 ```bash
 git log --oneline -30
-find . -maxdepth 3 -type f \( -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.md" \) \
-  ! -path "*/node_modules/*" ! -path "*/.git/*" ! -path "*/dist/*" | head -80
 cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || true
 head -120 README.md 2>/dev/null || true
-grep -rn "<PATTERNS>" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" --include="*.md" \
-  . 2>/dev/null | grep -v node_modules | grep -v dist | head -40
 ```
 
-Plus these MCP calls (also parallel):
+Plus these MCP calls (also parallel — **preferred over grep for symbol/pattern search**):
+- `mcp__monomind__monograph_query` — search for `<PATTERNS>` (see mode table below); replaces grep for symbol lookup
 - `mcp__monomind__monograph_god_nodes` — high-centrality modules (hotspots / where new features plug in)
 - `mcp__monomind__monograph_suggest` — query per mode below
 - `mcp__monomind__memory_search` — namespace `"mastermind:autodev"`, to exclude already-built work
 
+**Fallback only** (if monograph returns 0 results or DB not built):
+```bash
+grep -rn "<PATTERNS>" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" --include="*.md" \
+  . 2>/dev/null | grep -v node_modules | grep -v dist | head -40
+```
+
 Mode-specific values:
 
 | | Improvement loop | Feature pipeline |

package/.claude/skills/mastermind-skills/review.md

@@ -148,11 +148,14 @@ Run the test suite and adversarial probes against the live monofence-ai detector
 ```
 MONOFENCE INPUT BOUNDARY SCAN (monofence_deep flag):
 
-Step 1 — Find LLM input boundary files using these patterns:
-  grep -rl "detect\|isSafe\|prompt\|chat\|completion\|message" src/ --include="*.ts" --include="*.js"
-  find . -name "*.ts" -path "*/routes/*" -o -name "*.ts" -path "*/handlers/*" \
-         -o -name "*.ts" -path "*/controllers/*" -o -name "*.ts" -path "*/api/*" \
-         -o -name "prompt*.ts" -o -name "*chat*.ts" -o -name "*completion*.ts"
+Step 1 — Find LLM input boundary files:
+  PREFERRED: monograph_query({ query: "detect isSafe prompt chat completion message" })
+             monograph_neighbors({ name: "detect" })  // trace call chains into LLM boundaries
+  FALLBACK (if monograph returns 0 results):
+    grep -rl "detect\|isSafe\|prompt\|chat\|completion\|message" src/ --include="*.ts" --include="*.js"
+    find . -name "*.ts" -path "*/routes/*" -o -name "*.ts" -path "*/handlers/*" \
+           -o -name "*.ts" -path "*/controllers/*" -o -name "*.ts" -path "*/api/*" \
+           -o -name "prompt*.ts" -o -name "*chat*.ts" -o -name "*completion*.ts"
 
 Step 2 — For each boundary file found, extract string literals and template literals
   that flow into LLM calls (look for openai/anthropic/fetch calls).

package/.claude/skills/mastermind-skills/techport.md

@@ -75,8 +75,17 @@ find .claude -name "*.md" \
 
 ### 0B — Naming Convention Extraction (from actual monomind code)
 
-Extract the real conventions — not the stated ones — from the codebase itself:
+Extract the real conventions — not the stated ones — from the codebase itself.
 
+**Step 1 — monograph-based extraction (preferred):**
+```
+# Use monograph for exported symbol discovery
+monograph_query({ query: "export class interface" })    # all exported types
+monograph_god_nodes({})                                  # high-centrality files (naming exemplars)
+monograph_stats({})                                      # node counts by type
+```
+
+**Step 2 — grep fallback (only if monograph returns 0 results or DB not built):**
 ```bash
 BASE=packages/@monomind/cli/src
 
@@ -143,10 +152,20 @@ Domain vocab:       Agent, Memory, Swarm, Config, Node, Graph, Session, Task, Wo
 
 ### 0C — Dependency Direction Constraints
 
+**Preferred: monograph-based dependency analysis:**
+```
+# Use monograph for dependency direction mapping
+monograph_community({})                              # module clusters with import directions
+monograph_context({ name: "types" })                 # 360° view: importers vs imports
+monograph_context({ name: "utils" })
+monograph_context({ name: "core" })
+monograph_context({ name: "commands" })
+monograph_context({ name: "services" })
+```
+
+**Fallback (only if monograph unavailable):**
 ```bash
 BASE=packages/@monomind/cli/src
-
-# Map import directions by directory layer
 for dir in types utils core commands services; do
   count=$(grep -rn "^import" "$BASE/$dir" --include="*.ts" 2>/dev/null | wc -l)
   refs=$(grep -rn "from.*/$dir/" "$BASE" --include="*.ts" 2>/dev/null | wc -l)
@@ -160,6 +179,13 @@ Extract the implied layering from the import ratio. High `imported_by` → leaf/
 
 ### 0D — Build Monomind Vocabulary Name Set (for collision detection)
 
+**Preferred: monograph-based symbol enumeration:**
+```
+monograph_query({ query: "export class interface function const type enum" })
+# Extract names from results for collision checking
+```
+
+**Fallback (only if monograph unavailable):**
 ```bash
 grep -rhn "^export" packages/@monomind/cli/src \
   --include="*.ts" | grep -v dist | \
@@ -200,6 +226,14 @@ Set `source_brand` to the PascalCase result (e.g., `Monomind`, `ClaudeFlow`, `So
 
 ### 1B — Repo-Map (Structural Index)
 
+**If source project has a monograph index** (check with `monograph_health` against source_path):
+```
+monograph_query({ query: "export class interface function" })  # all exported symbols
+monograph_god_nodes({})                                         # high-centrality files
+monograph_community({})                                         # module structure
+```
+
+**Otherwise (foreign project without monograph — grep is expected here):**
 ```bash
 # File tree
 find "{source_path}" -maxdepth 4 \

package/.claude/skills/monodesign/document.md

@@ -16,15 +16,18 @@ Read `reference/document.md` from the monodesign skill directory for the full pr
 
 ## Discovery
 
-**Extract from codebase:**
+**Extract from codebase (monograph-first):**
+```
+# Preferred: monograph for design token discovery
+monograph_query({ query: "CSS custom properties variables tokens" })
+monograph_query({ query: "font-family font-face typography" })
+monograph_query({ query: "color theme palette" })
+```
+
+**Fallback (if monograph returns 0 results or DB not built):**
 ```bash
-# Find CSS custom properties
 grep -r "^--" src/ --include="*.css" --include="*.scss" -h | sort -u
-
-# Find font declarations
 grep -r "font-family\|@font-face\|@import.*font" src/ -h | sort -u
-
-# Find color values
 grep -rE "#[0-9a-fA-F]{3,8}|oklch\(|rgb\(|hsl\(" src/ -h | sort -u | head -50
 ```
 

package/.claude/skills/monodesign/extract.md

@@ -17,7 +17,7 @@ Every codebase with more than a few pages has an implicit design system — inco
 ## Discovery Phase
 
 **Color inventory**
-- Collect all color values used in the codebase (grep for `#`, `rgb`, `hsl`, `oklch`)
+- Collect all color values used in the codebase (use `monograph_query({ query: "color rgb hsl oklch" })` first; fall back to grep for `#`, `rgb`, `hsl`, `oklch` if monograph returns 0 results)
 - Group by apparent purpose (backgrounds, text, accents, borders, shadows)
 - Identify the brand anchor color(s)
 - Spot inconsistencies (5 slightly different grays)

package/.claude/skills/monodesign/reference/document.md

@@ -81,7 +81,7 @@ Decide by scanning first (Scan mode Step 1). If the scan finds no tokens, no com
 
 Search the codebase in priority order:
 
-1. **CSS custom properties**: grep for `--color-`, `--font-`, `--spacing-`, `--radius-`, `--shadow-`, `--ease-`, `--duration-` declarations in CSS files (usually `src/styles/`, `public/css/`, `app/globals.css`, etc.). Record name, value, and the file it's defined in.
+1. **CSS custom properties**: use `monograph_query({ query: "color font spacing radius shadow ease duration CSS custom property" })` first; fall back to grep for `--color-`, `--font-`, `--spacing-`, `--radius-`, `--shadow-`, `--ease-`, `--duration-` declarations in CSS files if monograph returns 0 results. Record name, value, and the file it's defined in.
 2. **Tailwind config**: if `tailwind.config.{js,ts,mjs}` exists, read the `theme.extend` block for colors, fontFamily, spacing, borderRadius, boxShadow.
 3. **CSS-in-JS theme files**: styled-components, emotion, vanilla-extract, stitches; look for `theme.ts`, `tokens.ts`, or equivalent.
 4. **Design token files**: `tokens.json`, `design-tokens.json`, Style Dictionary output, W3C token community group format.

package/.claude/skills/monodesign/reference/live.md

@@ -364,7 +364,7 @@ The goal is the same: give the user three variants to choose from AND persist th
 
 Use the error payload:
 
-- `element_not_in_source` with `generatedMatch: "public/docs/foo.html"`: the served HTML is generated. Find the generator (grep for writers of that path, e.g. `scripts/build-sub-pages.js`, an Astro/Next template) and locate the template or partial that emits this element.
+- `element_not_in_source` with `generatedMatch: "public/docs/foo.html"`: the served HTML is generated. Find the generator (use `monograph_query({ query: "build generate template" })` or `monograph_neighbors` to trace writers of that path; fall back to grep if monograph returns 0 results, e.g. `scripts/build-sub-pages.js`, an Astro/Next template) and locate the template or partial that emits this element.
 - `element_not_found`: the element is runtime-injected. Look for the component that renders it (React/Vue/Svelte), the JS that assembles it, or the data source that feeds it.
 - `file_is_generated` with `file: "..."`: user pointed at a generated file explicitly. Same resolution as `element_not_in_source`.
 

package/.claude/skills/monolean/SKILL.md

@@ -45,7 +45,7 @@ take the higher one and move on. The first lazy solution that works is the
 right one — once you actually know what the change has to touch.
 
 **Bug fix = root cause, not symptom.** A report names a symptom. Before you
-edit, grep every caller of the function you're about to touch. The lazy fix IS
+edit, find every caller of the function you're about to touch (use `monograph_neighbors` or `monograph_impact` first; fall back to grep only if monograph returns 0 results). The lazy fix IS
 the root-cause fix: one guard in the shared function is a smaller diff than a
 guard in every caller — and patching only the path the ticket names leaves
 every sibling caller still broken. Fix it once, where all callers route through.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "monomind",
-  "version": "1.18.15",
+  "version": "1.19.0",
   "description": "Monomind - Enterprise AI agent orchestration for Claude Code. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration",
   "main": "dist/index.js",
   "type": "module",

package/packages/@monomind/cli/.claude/agents/core/researcher.md

@@ -35,26 +35,29 @@ You are a research specialist focused on thorough investigation, pattern analysi
 
 ## Research Methodology
 
-### 1. Information Gathering
-- Use multiple search strategies (glob, grep, semantic search)
+### 1. Information Gathering (monograph-first)
+- **Always start with monograph** — call `monograph_query` or `monograph_suggest` before grep/find
+- Only fall back to grep/find if monograph returns 0 results or the DB is not built
 - Read relevant files completely for context
 - Check multiple locations for related information
-- Consider different naming conventions and patterns
 
 ### 2. Pattern Analysis
-```bash
-# Example search patterns
-- Implementation patterns: grep -r "class.*Controller" --include="*.ts"
-- Configuration patterns: glob "**/*.config.*"
-- Test patterns: grep -r "describe\|test\|it" --include="*.test.*"
-- Import patterns: grep -r "^import.*from" --include="*.ts"
+```
+# Preferred: monograph for symbol/definition lookups
+monograph_query({ query: "Controller" })           # find controller classes
+monograph_query({ query: "config" })                # find configuration patterns
+monograph_suggest({ task: "test patterns" })         # find test-related files
+
+# Fallback only (if monograph returns 0 results):
+grep -r "class.*Controller" --include="*.ts"
+grep -r "^import.*from" --include="*.ts"
 ```
 
 ### 3. Dependency Analysis
-- Track import statements and module dependencies
-- Identify external package dependencies
-- Map internal module relationships
-- Document API contracts and interfaces
+- **Use `monograph_neighbors` and `monograph_impact`** for dependency mapping
+- Call `monograph_god_nodes` for high-centrality files
+- Call `monograph_community` for module cluster boundaries
+- Fall back to grep on import statements only if monograph is unavailable
 
 ### 4. Documentation Mining
 - Extract inline comments and JSDoc
@@ -98,21 +101,23 @@ research_findings:
 
 ## Search Strategies
 
-### 1. Broad to Narrow
-```bash
-# Start broad
-glob "**/*.ts"
-# Narrow by pattern
+### 1. Monograph-First (preferred)
+```
+# Start with monograph for any symbol or code lookup
+monograph_query({ query: "symbol-name" })           # BM25 keyword search
+monograph_suggest({ task: "description of task" })   # ranked file suggestions
+monograph_neighbors({ name: "ClassName" })           # direct connections
+monograph_impact({ name: "functionName" })           # blast radius
+
+# Only if monograph returns 0 results or DB not built:
 grep -r "specific-pattern" --include="*.ts"
-# Focus on specific files
-read specific-file.ts
 ```
 
 ### 2. Cross-Reference
-- Search for class/function definitions
-- Find all usages and references
-- Track data flow through the system
-- Identify integration points
+- Use `monograph_neighbors` for usages and references
+- Use `monograph_shortest_path` to trace connections between modules
+- Use `monograph_context` for 360° view of a file
+- Fall back to grep only if monograph is unavailable
 
 ### 3. Historical Analysis
 - Review git history for context

package/packages/@monomind/cli/.claude/agents/github/code-review-swarm.md

@@ -2,7 +2,7 @@
 name: code-review-swarm
 description: |
   Deploy specialized AI agents to perform comprehensive, intelligent code reviews that go beyond traditional static analysis
-tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, Bash, Read, Write, TodoWrite
+tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, Bash, Read, Write, TodoWrite
 ---
 
 # Code Review Swarm - Automated Code Review with AI Agents

package/packages/@monomind/cli/.claude/agents/github/github-modes.md

@@ -2,7 +2,7 @@
 name: github-modes
 description: |
   Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization
-tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, Bash, TodoWrite, Read, Write
+tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, Bash, TodoWrite, Read, Write
 ---
 
 # GitHub Integration Modes

package/packages/@monomind/cli/.claude/agents/github/issue-tracker.md

@@ -2,7 +2,7 @@
 name: issue-tracker
 description: |
   Intelligent issue management and project coordination with automated tracking, progress monitoring, and team coordination
-tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_store, Bash, TodoWrite, Read, Write
+tools: mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_store, Bash, TodoWrite, Read, Write
 ---
 
 # GitHub Issue Tracker

package/packages/@monomind/cli/.claude/agents/github/multi-repo-swarm.md

@@ -1,7 +1,7 @@
 ---
 name: multi-repo-swarm
 description: Cross-repository swarm orchestration for organization-wide automation and intelligent collaboration
-tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__swarm_status, mcp__monomind__memory_usage, mcp__monomind__github_repo_analyze, mcp__monomind__github_pr_manage, mcp__monomind__github_sync_coord, mcp__monomind__github_metrics
+tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__swarm_status, mcp__monomind__memory_usage, mcp__monomind__github_repo_analyze, mcp__monomind__github_pr_manage, mcp__monomind__github_sync_coord, mcp__monomind__github_metrics
 ---
 
 # Multi-Repo Swarm - Cross-Repository Swarm Orchestration

package/packages/@monomind/cli/.claude/agents/github/pr-manager.md

@@ -2,7 +2,7 @@
 name: pr-manager
 description: |
   Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows
-tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__swarm_status, mcp__monomind__memory_store, mcp__monomind__github_pr_manage, mcp__monomind__github_code_review, mcp__monomind__github_metrics
+tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__swarm_status, mcp__monomind__memory_store, mcp__monomind__github_pr_manage, mcp__monomind__github_code_review, mcp__monomind__github_metrics
 ---
 
 # GitHub PR Manager

package/packages/@monomind/cli/.claude/agents/github/project-board-sync.md

@@ -2,7 +2,7 @@
 name: project-board-sync
 description: |
   Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination
-tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__swarm_status, mcp__monomind__memory_usage, mcp__monomind__github_repo_analyze, mcp__monomind__github_pr_manage, mcp__monomind__github_issue_track, mcp__monomind__github_metrics, mcp__monomind__workflow_create, mcp__monomind__workflow_execute
+tools: Bash, Read, Write, Edit, Glob, Grep, LS, TodoWrite, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__swarm_status, mcp__monomind__memory_usage, mcp__monomind__github_repo_analyze, mcp__monomind__github_pr_manage, mcp__monomind__github_issue_track, mcp__monomind__github_metrics, mcp__monomind__workflow_create, mcp__monomind__workflow_execute
 ---
 
 # Project Board Sync - GitHub Projects Integration

package/packages/@monomind/cli/.claude/agents/github/release-manager.md

@@ -2,7 +2,7 @@
 name: release-manager
 description: |
   Automated release coordination and deployment with Monomind swarm orchestration for seamless version management, testing, and deployment across multiple packages
-tools: Bash, Read, Write, Edit, TodoWrite, TodoRead, Task, WebFetch, mcp__github__create_pull_request, mcp__github__merge_pull_request, mcp__github__create_branch, mcp__github__push_files, mcp__github__create_issue, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_store
+tools: Bash, Read, Write, Edit, TodoWrite, TodoRead, Task, WebFetch, mcp__github__create_pull_request, mcp__github__merge_pull_request, mcp__github__create_branch, mcp__github__push_files, mcp__github__create_issue, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_store
 ---
 
 # GitHub Release Manager

package/packages/@monomind/cli/.claude/agents/github/repo-architect.md

@@ -2,7 +2,7 @@
 name: repo-architect
 description: |
   Repository structure optimization and multi-repo management with Monomind swarm coordination for scalable project architecture and development workflows
-tools: Bash, Read, Write, Edit, LS, Glob, TodoWrite, TodoRead, Task, WebFetch, mcp__github__create_repository, mcp__github__fork_repository, mcp__github__search_repositories, mcp__github__push_files, mcp__github__create_or_update_file, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_store
+tools: Bash, Read, Write, Edit, LS, Glob, TodoWrite, TodoRead, Task, WebFetch, mcp__github__create_repository, mcp__github__fork_repository, mcp__github__search_repositories, mcp__github__push_files, mcp__github__create_or_update_file, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_store
 ---
 
 # GitHub Repository Architect

package/packages/@monomind/cli/.claude/agents/github/swarm-issue.md

@@ -2,7 +2,7 @@
 name: swarm-issue
 description: |
   GitHub issue-based swarm coordination agent that transforms issues into intelligent multi-agent tasks with automatic decomposition and progress tracking
-tools: mcp__github__get_issue, mcp__github__create_issue, mcp__github__update_issue, mcp__github__list_issues, mcp__github__create_issue_comment, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_usage, TodoWrite, TodoRead, Bash, Grep, Read, Write
+tools: mcp__github__get_issue, mcp__github__create_issue, mcp__github__update_issue, mcp__github__list_issues, mcp__github__create_issue_comment, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_usage, TodoWrite, TodoRead, Bash, Grep, Read, Write
 ---
 
 # Swarm Issue - Issue-Based Swarm Coordination

package/packages/@monomind/cli/.claude/agents/github/swarm-pr.md

@@ -2,7 +2,7 @@
 name: swarm-pr
 description: |
   Pull request swarm management agent that coordinates multi-agent code review, validation, and integration workflows with automated PR lifecycle management
-tools: mcp__github__get_pull_request, mcp__github__create_pull_request, mcp__github__update_pull_request, mcp__github__list_pull_requests, mcp__github__create_pr_comment, mcp__github__get_pr_diff, mcp__github__merge_pull_request, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_usage, mcp__monomind__coordination_sync, TodoWrite, TodoRead, Bash, Grep, Read, Write, Edit
+tools: mcp__github__get_pull_request, mcp__github__create_pull_request, mcp__github__update_pull_request, mcp__github__list_pull_requests, mcp__github__create_pr_comment, mcp__github__get_pr_diff, mcp__github__merge_pull_request, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_usage, mcp__monomind__coordination_sync, TodoWrite, TodoRead, Bash, Grep, Read, Write, Edit
 ---
 
 # Swarm PR - Managing Swarms through Pull Requests

package/packages/@monomind/cli/.claude/agents/github/sync-coordinator.md

@@ -2,7 +2,7 @@
 name: sync-coordinator
 description: |
   Multi-repository synchronization coordinator that manages version alignment, dependency synchronization, and cross-package integration with intelligent swarm orchestration
-tools: mcp__github__push_files, mcp__github__create_or_update_file, mcp__github__get_file_contents, mcp__github__create_pull_request, mcp__github__search_repositories, mcp__github__list_repositories, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_store, mcp__monomind__coordination_sync, mcp__monomind__load_balance, TodoWrite, TodoRead, Bash, Read, Write, Edit, MultiEdit
+tools: mcp__github__push_files, mcp__github__create_or_update_file, mcp__github__get_file_contents, mcp__github__create_pull_request, mcp__github__search_repositories, mcp__github__list_repositories, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_store, mcp__monomind__coordination_sync, mcp__monomind__load_balance, TodoWrite, TodoRead, Bash, Read, Write, Edit, MultiEdit
 ---
 
 # GitHub Sync Coordinator

package/packages/@monomind/cli/.claude/agents/github/workflow-automation.md

@@ -2,7 +2,7 @@
 name: workflow-automation
 description: |
   GitHub Actions workflow automation agent that creates intelligent, self-organizing CI/CD pipelines with adaptive multi-agent coordination and automated optimization
-tools: mcp__github__create_workflow, mcp__github__update_workflow, mcp__github__list_workflows, mcp__github__get_workflow_runs, mcp__github__create_workflow_dispatch, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__task_orchestrate, mcp__monomind__memory_usage, mcp__monomind__performance_report, mcp__monomind__bottleneck_analyze, mcp__monomind__workflow_create, mcp__monomind__automation_setup, TodoWrite, TodoRead, Bash, Read, Write, Edit, Grep
+tools: mcp__github__create_workflow, mcp__github__update_workflow, mcp__github__list_workflows, mcp__github__get_workflow_runs, mcp__github__create_workflow_dispatch, mcp__monomind__swarm_init, mcp__monomind__agent_spawn, mcp__monomind__memory_usage, mcp__monomind__performance_report, mcp__monomind__bottleneck_analyze, mcp__monomind__workflow_create, mcp__monomind__automation_setup, TodoWrite, TodoRead, Bash, Read, Write, Edit, Grep
 ---
 
 # Workflow Automation - GitHub Actions Integration

package/packages/@monomind/cli/.claude/agents/goal/goal-planner.md

@@ -87,7 +87,7 @@ Advanced action definitions with tool groups:
 Action: analyze_codebase
   Preconditions: {repository_accessible: true}
   Effects: {code_analyzed: true, metrics_available: true}
-  Tools: [grep, ast_parser, complexity_analyzer]
+  Tools: [monograph_query, monograph_suggest, grep (fallback), ast_parser, complexity_analyzer]
   Execution: hybrid (LLM for insights, code for metrics)
   Cost: 2
   Fallback: manual_review if tools unavailable

package/packages/@monomind/cli/.claude/agents/specialized/specialized-workflow-architect.md

@@ -440,27 +440,24 @@ Use this when joining a new project or auditing an existing system:
 
 ### Step 0: Discovery Pass (always first)
 
-Before designing anything, discover what already exists:
+Before designing anything, discover what already exists. **Use monograph first** — fall back to grep only if monograph returns 0 results or the DB is not built.
+
+```
+# PREFERRED: monograph-based discovery
+monograph_query({ query: "route handler" })          # find all route entry points
+monograph_query({ query: "worker job consumer" })    # find background processors
+monograph_query({ query: "state transition status" })# find state machines
+monograph_route_map({})                              # list all HTTP routes with handlers
+monograph_suggest({ task: "workflow entry points, workers, state machines, cron jobs" })
+```
 
 ```bash
-# Find all workflow entry points (adapt patterns to your framework)
+# FALLBACK (only if monograph returns 0 results):
 grep -rn "router\.\(post\|put\|delete\|get\|patch\)" src/routes/ --include="*.ts" --include="*.js"
 grep -rn "@app\.\(route\|get\|post\|put\|delete\)" src/ --include="*.py"
-grep -rn "HandleFunc\|Handle(" cmd/ pkg/ --include="*.go"
-
-# Find all background workers / job processors
 find src/ -type f -name "*worker*" -o -name "*job*" -o -name "*consumer*" -o -name "*processor*"
-
-# Find all state transitions in the codebase
 grep -rn "status.*=\|\.status\s*=\|state.*=\|\.state\s*=" src/ --include="*.ts" --include="*.py" --include="*.go" | grep -v "test\|spec\|mock"
-
-# Find all database migrations
 find . -path "*/migrations/*" -type f | head -30
-
-# Find all infrastructure resources
-find . -name "*.tf" -o -name "docker-compose*.yml" -o -name "*.yaml" | xargs grep -l "resource\|service:" 2>/dev/null
-
-# Find all scheduled / cron jobs
 grep -rn "cron\|schedule\|setInterval\|@Scheduled" src/ --include="*.ts" --include="*.py" --include="*.go" --include="*.java"
 ```
 

package/packages/@monomind/cli/.claude/agents/testing/production-validator.md

@@ -245,17 +245,18 @@ describe('Performance Validation', () => {
 
 ### 1. Code Quality Validation
 
+**Preferred: monograph-based code quality scan:**
+```
+monograph_query({ query: "mock fake stub" })         # find mock implementations in prod code
+monograph_query({ query: "TODO FIXME" })             # find unfinished work in critical paths
+monograph_query({ query: "console log warn error" }) # find console statements
+```
+
+**Fallback (if monograph returns 0 results or DB not built):**
 ```bash
-# No mock implementations in production code
 grep -r "mock\|fake\|stub" src/ --exclude-dir=__tests__ --exclude="*.test.*" --exclude="*.spec.*"
-
-# No TODO/FIXME in critical paths
 grep -r "TODO\|FIXME" src/ --exclude-dir=__tests__
-
-# No hardcoded test data
 grep -r "test@\|example\|localhost" src/ --exclude-dir=__tests__
-
-# No console.log statements
 grep -r "console\." src/ --exclude-dir=__tests__
 ```
 

package/packages/@monomind/cli/.claude/agents/testing/testing-evidence-collector.md

@@ -47,7 +47,9 @@ You are **EvidenceQA**, a skeptical QA specialist who requires visual proof for
 # 2. Check what's actually built
 ls -la resources/views/ || ls -la *.html
 
-# 3. Reality check for claimed features  
+# 3. Reality check for claimed features (monograph-first, grep fallback)
+# Preferred: monograph_query({ query: "luxury premium glass morphism" })
+# Fallback:
 grep -r "luxury\|premium\|glass\|morphism" . --include="*.html" --include="*.css" --include="*.blade.php" || echo "NO PREMIUM FEATURES FOUND"
 
 # 4. Review comprehensive test results

package/packages/@monomind/cli/.claude/commands/mastermind/code-review.md

@@ -66,10 +66,10 @@ Based on `STACK`, determine which specialist agents to run beyond the always-on
 - `Security Engineer` — injection, auth gaps, secrets exposure, CVE-prone patterns, OWASP Top 10
 - `Reality Checker` — evidence-based assessment: does the code actually do what it claims?
 
-**Run conditionally** — detect by running these checks and adding the agent if exit 0:
-- `Accessibility Auditor` — `find . -maxdepth 5 \( -name "*.html" -o -name "*.jsx" -o -name "*.tsx" \) -not -path "*/node_modules/*" | head -1 | grep -q .`
-- `API Tester` — `find . -maxdepth 5 \( -name "*.route.*" -o -name "openapi.yml" -o -name "openapi.json" -o -name "swagger.*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "express\(|fastify|hono|koa|router\." --include="*.ts" --include="*.js" . 2>/dev/null`
-- `Database Optimizer` — `find . -maxdepth 5 \( -name "*.sql" -o -name "*migration*" -o -name "*schema*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "prisma|typeorm|sequelize|drizzle|knex" --include="*.ts" --include="*.js" . 2>/dev/null`
+**Run conditionally** — use `monograph_query` first to detect stack; fall back to find/grep if monograph returns 0 results:
+- `Accessibility Auditor` — `monograph_query({ query: "html jsx tsx component" })` or `find . -maxdepth 5 \( -name "*.html" -o -name "*.jsx" -o -name "*.tsx" \) -not -path "*/node_modules/*" | head -1 | grep -q .`
+- `API Tester` — `monograph_query({ query: "express fastify hono koa router route openapi swagger" })` or `find . -maxdepth 5 \( -name "*.route.*" -o -name "openapi.yml" -o -name "openapi.json" -o -name "swagger.*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "express\(|fastify|hono|koa|router\." --include="*.ts" --include="*.js" . 2>/dev/null`
+- `Database Optimizer` — `monograph_query({ query: "prisma typeorm sequelize drizzle knex sql migration schema" })` or `find . -maxdepth 5 \( -name "*.sql" -o -name "*migration*" -o -name "*schema*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "prisma|typeorm|sequelize|drizzle|knex" --include="*.ts" --include="*.js" . 2>/dev/null`
 - `SRE` — `find . -maxdepth 3 \( -name "Dockerfile" -o -name "docker-compose*" -o -name "*.yml" -path "*/.github/workflows/*" \) | head -1 | grep -q .`
 - `Mobile App Builder` — `find . -maxdepth 3 \( -name "*.swift" -o -name "*.kt" \) | head -1 | grep -q . || grep -q "react-native" package.json 2>/dev/null`
 

package/packages/@monomind/cli/.claude/commands/mastermind/help.md

@@ -97,8 +97,8 @@ mcp__monomind__memory_store({ key: "...", value: "...", namespace: "..." })
 mcp__monomind__memory_search({ query: "...", namespace: "..." })
 
 // Knowledge graph
-mcp__monomind__graphify_suggest({ task: "..." })
-mcp__monomind__graphify_query({ query: "..." })
+mcp__monomind__monograph_suggest({ task: "..." })
+mcp__monomind__monograph_query({ query: "..." })
 
 // Swarm
 mcp__monomind__swarm_init({ topology: "hierarchical", maxAgents: 8, strategy: "specialized" })

package/packages/@monomind/cli/.claude/commands/mastermind/okf-export.md

@@ -0,0 +1,14 @@
+<!-- Export the Second Brain knowledge base as a portable OKF (Open Knowledge Format) bundle. -->
+
+Parse `$ARGUMENTS` for:
+- `--output <dir>` or `-o <dir>` → output directory (default: `.monomind/knowledge-export`)
+- `--scope <name>` or `-s <name>` → knowledge scope (default: `shared`)
+- Remaining positional arg → treated as output directory
+
+Run the export:
+
+```bash
+npx monomind doc export -o "<output_dir>" -s "<scope>"
+```
+
+After completion, report what was exported and where. If 0 documents exported, suggest `monomind doc ingest <path>` first.

package/packages/@monomind/cli/.claude/commands/mastermind/okf-import.md

@@ -0,0 +1,15 @@
+<!-- Import an OKF (Open Knowledge Format) bundle into the Second Brain knowledge base. -->
+
+Parse `$ARGUMENTS` for:
+- `--scope <name>` or `-s <name>` → knowledge scope (default: `shared`)
+- Remaining positional arg → bundle directory path (REQUIRED)
+
+If no bundle directory provided, ask: "Which directory contains the OKF bundle to import?"
+
+Run the import:
+
+```bash
+npx monomind doc ingest "<bundle_dir>" -s "<scope>"
+```
+
+After completion, report files processed, chunks indexed, and any errors. If the bundle directory doesn't exist or contains no `.md` files, say so.