agentsys 5.0.3 → 5.1.0

package/adapters/codex/skills/debate/SKILL.md

@@ -0,0 +1,214 @@
+---
+name: debate
+description: "Use when user asks to \"debate\", \"argue about\", \"compare perspectives\", \"stress test idea\", \"devil advocate\", \"codex vs gemini\". Runs structured multi-round debate between two AI tools with proposer/challenger roles."
+---
+
+# /debate - Structured AI Dialectic
+
+You are executing the /debate command. Your job is to parse the user's request, resolve missing parameters interactively, and spawn the debate orchestrator.
+
+## Constraints
+
+- NEVER expose API keys in commands or output
+- NEVER run with permission-bypassing flags
+- MUST validate tool names against allow-list: gemini, codex, claude, opencode, copilot
+- Proposer and challenger MUST be different tools
+- Rounds MUST be 1-5 (default: 2)
+
+## Execution
+
+### Phase 1: Parse Input (Flags + Natural Language)
+
+Parse `$ARGUMENTS` using both explicit flags and natural language. Flags take priority.
+
+#### Step 1a: Extract explicit flags
+
+1. `--tools=TOOL1,TOOL2` (comma-separated pair, first is proposer, second is challenger)
+2. `--rounds=N` where N is 1-5
+3. `--effort=VALUE` where VALUE is one of: low, medium, high, max
+4. `--model-proposer=VALUE` (any string)
+5. `--model-challenger=VALUE` (any string)
+6. `--context=VALUE` where VALUE is: diff, file=PATH, or none (passed through to consult skill for each tool invocation)
+
+Remove matched flags from `$ARGUMENTS`.
+
+#### Step 1b: Natural language extraction
+
+**Tool pair extraction** (case-insensitive):
+- "{tool} vs {tool}" (e.g., "codex vs gemini") -> proposer, challenger
+- "{tool} and {tool}" -> proposer, challenger
+- "with {tool} and {tool}" -> proposer, challenger
+- "between {tool} and {tool}" -> proposer, challenger
+- Tool names: claude, gemini, codex, opencode, copilot
+
+**Rounds extraction**:
+- "{N} rounds" -> rounds=N
+- "single round" / "one round" -> rounds=1
+- "deep" / "extended" -> rounds=3
+
+**Effort extraction** (same as consult):
+- "quick" / "fast" -> effort=low
+- "thorough" / "deep" / "carefully" -> effort=high
+- "maximum" / "max effort" -> effort=max
+
+**Topic extraction**:
+- Text after "about" is the topic
+- If no "about" pattern, remaining text after removing tool/rounds/effort markers
+
+**Validation**: rounds must be 1-5. Proposer and challenger must differ. If same tool specified for both, show: `[ERROR] Proposer and challenger must be different tools.`
+
+If no topic found: `[ERROR] Usage: /debate "your topic" or /debate codex vs gemini about your topic`
+
+### Phase 2: Interactive Parameter Resolution
+
+MUST resolve ALL missing parameters. Do NOT silently default.
+
+#### Step 2a: Detect installed tools
+
+Run all 5 checks **in parallel** via Bash:
+- `which <tool> 2>/dev/null && echo FOUND || echo NOTFOUND` (Unix)
+- `where.exe <tool> 2>nul && echo FOUND || echo NOTFOUND` (Windows)
+
+Check for: claude, gemini, codex, opencode, copilot.
+
+If fewer than 2 tools installed: `[ERROR] Debate requires at least 2 AI CLI tools. Install more: npm i -g @anthropic-ai/claude-code, npm i -g @openai/codex`
+
+#### Step 2b: Batch selection for missing params
+
+Use a SINGLE request_user_input call for all missing params:
+
+```
+request_user_input:
+> **Codex**: Each question MUST include a unique `id` field (e.g., `id: "q1"`).
+  questions:
+    - id: "debate-proposer"
+      header: "Proposer"                         # SKIP if proposer resolved
+      question: "Which tool should PROPOSE (argue for)?"
+      options (only installed tools):
+        - label: "Claude"       description: "Deep code reasoning"
+        - label: "Gemini"       description: "Fast multimodal analysis"
+        - label: "Codex"        description: "Agentic coding"
+        - label: "OpenCode"     description: "Flexible model choice"
+        - label: "Copilot"      description: "GitHub-integrated AI"
+
+    - id: "debate-challenger"
+      header: "Challenger"                       # SKIP if challenger resolved
+      question: "Which tool should CHALLENGE (find flaws)?"
+      options (only installed, excluding proposer):
+        [same list minus the proposer tool]
+
+    - id: "debate-effort"
+      header: "Effort"                           # SKIP if effort resolved
+      question: "What thinking effort level?"
+      options:
+        - label: "High (Recommended)"    description: "Thorough analysis for debate"
+        - label: "Medium"                description: "Balanced speed and quality"
+        - label: "Low"                   description: "Fast, minimal reasoning"
+        - label: "Max"                   description: "Maximum reasoning depth"
+
+    - id: "debate-rounds"
+      header: "Rounds"                           # SKIP if rounds resolved
+      question: "How many debate rounds?"
+      options:
+        - label: "2 (Recommended)"       description: "Propose + challenge + defend + respond"
+        - label: "1 (Quick)"             description: "Single propose + challenge"
+        - label: "3 (Extended)"          description: "Three full exchanges"
+        - label: "5 (Exhaustive)"        description: "Five rounds, deep exploration"
+
+    - id: "debate-context"
+      header: "Context"                          # SKIP if --context resolved
+      question: "Include codebase context for both tools?"
+      options:
+        - label: "None (Recommended)"    description: "No extra context, just the topic"
+        - label: "Diff"                  description: "Include current git diff"
+        - label: "File"                  description: "Include a specific file (will ask path)"
+```
+
+Map choices: "Claude" -> "claude", "High (Recommended)" -> "high", "2 (Recommended)" -> 2, "None (Recommended)" -> "none", "Diff" -> "diff", "File" -> "file" (then ask for path). Strip " (Recommended)" suffix.
+
+If context resolved to "file":
+  Use a follow-up request_user_input to ask for the file path:
+  ```
+  request_user_input:
+> **Codex**: Each question MUST include a unique `id` field (e.g., `id: "q1"`).
+    questions:
+      - id: "debate-file-path"
+        header: "File path"
+        question: "Which file should both tools see?"
+        options:
+          - label: "src/"               description: "Source directory file"
+          - label: "README.md"          description: "Project readme"
+  ```
+  The user can type any path via "Other".
+  After getting the path:
+  1. Reject absolute paths outside the current working directory
+  2. Reject paths containing `..` that escape the project root
+  3. Reject UNC paths (`\\` or `//` prefix)
+  4. Validate the file exists using the Read tool
+  If the path escapes the project: `[ERROR] Context file must be within the project directory`
+  If the file doesn't exist: `[ERROR] Context file not found: {PATH}`
+  If valid, set context to `file={user_provided_path}`.
+
+If proposer and challenger resolve to the same tool after selection, show error and re-ask for challenger.
+
+### Phase 3: Spawn Debate Orchestrator
+
+With all parameters resolved, spawn the debate orchestrator agent:
+
+```
+Task:
+  subagent_type: "debate:debate-orchestrator"
+  model: opus
+  prompt: |
+    Execute a structured debate with these pre-resolved parameters:
+    - topic: [topic]
+    - proposer: [proposer tool]
+    - challenger: [challenger tool]
+    - effort: [effort]
+    - rounds: [rounds]
+    - model_proposer: [model or "omit"]
+    - model_challenger: [model or "omit"]
+
+    If model is "omit" or empty, do NOT include --model in consult skill invocations. The consult skill will use effort-based defaults.
+    - context: [context or "none"]
+
+    Follow the debate skill templates. Display each round progressively.
+    Deliver a verdict that picks a winner.
+```
+
+### Phase 4: Present Results
+
+Display the orchestrator's output directly. It includes:
+- Progressive round-by-round output (displayed as each round completes)
+- Final synthesis with verdict, agreements, disagreements, and recommendation
+
+On failure: `[ERROR] Debate Failed: {specific error message}`
+
+## Error Handling
+
+| Error | Output |
+|-------|--------|
+| No topic provided | `[ERROR] Usage: /debate "your topic" or /debate codex vs gemini about your topic` |
+| Tool not installed | `[ERROR] {tool} is not installed. Install with: {install command}` |
+| Fewer than 2 tools | `[ERROR] Debate requires at least 2 AI CLI tools installed.` |
+| Same tool for both | `[ERROR] Proposer and challenger must be different tools.` |
+| Rounds out of range | `[ERROR] Rounds must be 1-5. Got: {rounds}` |
+| Context file not found | `[ERROR] Context file not found: {PATH}` |
+| Orchestrator fails | `[ERROR] Debate failed: {error}` |
+
+## Example Usage
+
+```bash
+# Natural language
+/debate codex vs gemini about microservices vs monolith
+/debate with claude and codex about our auth implementation
+/debate thoroughly gemini vs codex about database schema design
+/debate codex vs gemini 3 rounds about event sourcing
+
+# Explicit flags
+/debate "Should we use event sourcing?" --tools=claude,gemini --rounds=3 --effort=high
+/debate "Redis vs PostgreSQL for caching" --tools=codex,opencode
+
+# Mixed
+/debate codex vs gemini --effort=max about performance optimization strategies
+```

package/adapters/codex/skills/delivery-approval/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: delivery-approval
 description: "Use when user asks to \"validate delivery\", \"approve for shipping\", \"check if ready to ship\", \"verify task completion\". Autonomous validation that tests pass, build succeeds, and requirements are met."

package/adapters/codex/skills/deslop/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: deslop
 description: "Use when user asks to \"clean up slop\", \"remove AI artifacts\", \"deslop the codebase\", \"find debug statements\", \"remove console.logs\", \"repo hygiene\". Detects and removes AI-generated slop patterns."

package/adapters/codex/skills/drift-detect/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: drift-detect
 description: "Use when user asks to \"check plan drift\", \"compare docs to code\", \"verify roadmap\", \"scan for reality gaps\". Analyzes documentation vs actual code to detect drift and outdated plans."

package/adapters/codex/skills/enhance/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: enhance
 description: "Use when user asks to \"enhance prompts\", \"improve agents\", \"analyze plugins\", \"optimize documentation\", \"review CLAUDE.md\". Runs 5 parallel analyzers on prompts, agents, plugins, docs, and project memory files."

package/adapters/codex/skills/learn/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: learn
 description: "Use when user asks to \"learn about topic\", \"research subject\", \"create learning guide\", \"build knowledge base\", \"study topic\". Gathers online sources and synthesizes comprehensive guide with RAG index."

package/adapters/codex/skills/next-task/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: next-task
 description: "Use when user asks to \"find next task\", \"what should I work on\", \"automate workflow\", \"implement and ship\", \"run next-task\". Orchestrates complete task-to-production workflow: discovery, implementation, review, and delivery."

package/adapters/codex/skills/perf/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: perf
 description: "Use when user asks to \"run perf\", \"performance investigation\", \"benchmark regression\", \"profiling workflow\", \"baseline performance\". Runs structured perf investigations with baselines, profiling, hypotheses, and decisions."

package/adapters/codex/skills/repo-map/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: repo-map
 description: "Use when user asks to \"create repo map\", \"generate repo map\", \"update repo map\", \"repo map status\", \"map symbols\". Builds and updates AST-based repo map using ast-grep."

package/adapters/codex/skills/ship/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ship
 description: "Use when user asks to \"ship this\", \"create PR\", \"merge to main\", \"deploy changes\", \"push to production\". Complete PR workflow: commit, create PR, monitor CI, merge, deploy, validate."

package/adapters/codex/skills/ship-ci-review-loop/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ship-ci-review-loop
 description: "Use when monitoring CI and handling review comments during /ship. Details mandatory wait periods, auto-reviewer handling, and comment resolution."

package/adapters/codex/skills/ship-deployment/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ship-deployment
 description: "Use when deploying and validating during /ship. Details Railway/Vercel deployment, smoke testing, and rollback procedures."

package/adapters/codex/skills/ship-error-handling/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ship-error-handling
 description: "Use when handling and recovering from /ship command errors."

package/adapters/codex/skills/sync-docs/SKILL.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: sync-docs
 description: "Use when user asks to \"update docs\", \"sync documentation\", \"fix outdated docs\", \"refresh README\". Compares documentation to actual code and fixes discrepancies."

package/adapters/opencode/agents/agent-enhancer.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: agent-enhancer
 description: Analyze agent prompts for optimization opportunities

package/adapters/opencode/agents/agnix-agent.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: agnix-agent
 description: Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.

package/adapters/opencode/agents/ci-fixer.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ci-fixer
 description: Fix CI failures and PR comments. Use this agent when ci-monitor detects issues that need code changes.

package/adapters/opencode/agents/ci-monitor.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: ci-monitor
 description: Monitor CI status and PR comments with sleep/check loops. Use this agent after PR creation to watch for issues and delegate fixes to ci-fixer.

package/adapters/opencode/agents/claudemd-enhancer.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: claudemd-enhancer
 description: Analyzes and optimizes CLAUDE.md/AGENTS.md project memory files for better AI understanding

package/adapters/opencode/agents/consult-agent.md

@@ -1,7 +1,6 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: consult-agent
-description: "Execute cross-tool AI consultations via Task spawning. Use when agents or workflows need a second opinion from Gemini, Codex, Claude, OpenCode, or Copilot."
+description: "Execute cross-tool AI consultations via Task spawning. Use when agents or workflows need a second opinion from Gemini, Codex, Claude, OpenCode, or Copilot. Supports multi-instance parallel consultations (count > 1)."
 mode: subagent
 ---
 
@@ -17,11 +16,13 @@ mode: subagent
 
 You are the programmatic interface for cross-tool AI consultations. The consult plugin follows the standard Command -> Agent -> Skill pattern:
 
-- **Command** (`/consult`): User-facing entry point. Handles interactive parameter selection (tool picker, effort picker, model picker via AskUserQuestion). Invokes the consult skill directly. Does NOT spawn this agent.
-- **Agent** (this file): Programmatic entry point for other agents and workflows via Task(). Requires all parameters pre-resolved by the caller. Invokes the consult skill, then executes the CLI command it returns via Bash.
-- **Skill** (`consult`): Implementation source of truth. Provides provider configurations, model mappings, command templates, context packaging, and output parsing logic. Both the command and this agent invoke the skill before executing anything.
+- **Command** (`/consult`): User-facing entry point. Handles natural language parsing and interactive parameter selection. For single instance (count=1), invokes the consult skill directly. For multi-instance (count>1), spawns this agent.
+- **Agent** (this file): Programmatic entry point. Requires all parameters pre-resolved by the caller. Handles both single-instance (invoke skill) and multi-instance (parallel execution). Used by the command for multi-instance and by other agents/workflows via Task().
+- **Skill** (`consult`): Implementation source of truth. Provides provider configurations, model mappings, command templates, context packaging, and output parsing logic.
 
-Use this agent when the /consult command is not available (e.g., from other agents or automated workflows that need a second opinion).
+Use this agent for:
+1. Multi-instance consultations (count > 1) dispatched by the /consult command
+2. Programmatic consultations from other agents or automated workflows
 
 ## Why Sonnet Model
 
@@ -43,13 +44,28 @@ Extract from prompt. ALL parameters MUST be pre-resolved by the caller (the /con
 - **context**: Context mode (diff, file, none) - default: none
 - **continueSession**: Session ID or true/false
 - **sessionFile**: Path to session state file
+- **count**: Number of parallel instances (1-5, default: 1)
 
 If any required parameter is missing, return an error as plain JSON:
 ```json
 {"error": "Missing required parameter: [param]. The caller must resolve all parameters before spawning this agent."}
 ```
 
-### 2. Invoke Consult Skill (MUST)
+### 2. Route: Single vs Multi-Instance
+
+If both `continueSession` is set and `count > 1`, return:
+```json
+{"error": "Cannot use --continue with count > 1. Session resume applies to a single tool session."}
+```
+
+Validate count: if provided, must be 1-5. If out of range, return `{"error": "Instance count must be 1-5. Got: [count]"}`.
+
+If `count` is 1 (or not provided), follow the **Single Instance** path (Step 3).
+If `count` is 2-5, follow the **Multi-Instance** path (Step 4).
+
+### 3. Single Instance (count=1)
+
+#### 3a. Invoke Consult Skill (MUST)
 
 You MUST invoke the `consult` skill using the Skill tool. Pass all parsed arguments. The skill is the authoritative source for provider configurations, model mappings, command building, context packaging, session loading, and output parsing. Do not bypass the skill.
 
@@ -60,11 +76,11 @@ Args: [question] --tool=[tool] --effort=[effort] [--model=[model]] [--context=[c
 Example: "Review this function" --tool=claude --effort=high --model=opus
 ```
 
-### 3. Execute Command
+#### 3b. Execute Command
 
 Run the CLI command returned by the skill via Bash with a 120-second timeout.
 
-### 4. Parse and Return Result
+#### 3c. Parse and Return Result
 
 Parse the response using the method specified by the skill for the target tool, then format and display the result as human-friendly text:
 
@@ -77,10 +93,105 @@ The results of the consultation are:
 
 Set `continuable: true` for Claude, Gemini, Codex, and OpenCode (tools with session resume support). Only Copilot is non-continuable. Each tool uses a different resume mechanism: Claude/Gemini use `--resume`, Codex uses `codex exec resume`, OpenCode uses `--session`/`--continue`.
 
-### 5. Save Session State
+#### 3d. Save Session State
 
 Write session state to the sessionFile path provided by the command for continuity.
 
+### 4. Multi-Instance (count > 1)
+
+When count > 1, execute N parallel consultations with the same tool and parameters.
+
+#### 4a. Invoke Consult Skill Once
+
+Invoke the `consult` skill once to get the resolved command template and provider configuration. This gives you the exact CLI command to run for this tool/model/effort combination. Do NOT execute the command from the skill response yet.
+
+#### 4b. Write Indexed Temp Files
+
+Write the question to N indexed temp files using the Write tool:
+- `{AI_STATE_DIR}/consult/question-1.tmp`
+- `{AI_STATE_DIR}/consult/question-2.tmp`
+- ... through `question-{count}.tmp`
+
+Platform state directory:
+- Claude Code: `.claude/`
+- OpenCode: `.opencode/`
+- Codex CLI: `.codex/`
+
+All temp files contain the same question text (with context prepended if applicable).
+
+#### 4c. Execute N Commands in Parallel
+
+Run N Bash commands **in parallel** (multiple Bash tool calls in a single message). Each command uses the template from Step 4a but points to its own indexed temp file. Set 120-second timeout on each.
+
+Example for 3 parallel Codex calls:
+```
+Bash: codex exec "$(cat "{AI_STATE_DIR}/consult/question-1.tmp")" --json -m "gpt-5.3-codex" -c model_reasoning_effort="high"
+Bash: codex exec "$(cat "{AI_STATE_DIR}/consult/question-2.tmp")" --json -m "gpt-5.3-codex" -c model_reasoning_effort="high"
+Bash: codex exec "$(cat "{AI_STATE_DIR}/consult/question-3.tmp")" --json -m "gpt-5.3-codex" -c model_reasoning_effort="high"
+```
+
+#### 4d. Parse and Format Results
+
+Parse each response using the skill's output parsing rules for the target tool. Format as numbered responses:
+
+```
+# Multi-Consultation Results
+
+Tool: {tool}, Model: {model}, Effort: {effort}, Instances: {count}
+
+---
+
+## Response 1 (Duration: {duration_ms}ms)
+
+{response_1}
+
+---
+
+## Response 2 (Duration: {duration_ms}ms)
+
+{response_2}
+
+---
+
+[... for each instance ...]
+
+---
+
+## Synthesis
+
+Key agreement points:
+- [Common themes across responses]
+
+Key differences:
+- [Where responses diverge]
+```
+
+If some instances failed but others succeeded, show the successful responses and note failures:
+`[WARN] Instance {N} failed: {error}. Showing {M} of {count} responses.`
+
+#### 4e. Clean Up and Save State
+
+1. Delete all indexed temp files (`question-1.tmp` through `question-{count}.tmp`)
+2. Save multi-session state to `{AI_STATE_DIR}/consult/last-multi-session.json`:
+
+```json
+{
+  "tool": "codex",
+  "model": "gpt-5.3-codex",
+  "effort": "high",
+  "count": 3,
+  "timestamp": "{ISO 8601 timestamp of execution}",
+  "question": "original question text",
+  "sessions": [
+    {"session_id": "abc-123", "continuable": true},
+    {"session_id": "def-456", "continuable": true},
+    {"session_id": "ghi-789", "continuable": true}
+  ]
+}
+```
+
+3. Also save the first session to `{AI_STATE_DIR}/consult/last-session.json` (standard format) so `--continue` works.
+
 ## Error Handling
 
 | Error | Action |
@@ -93,26 +204,7 @@ Write session state to the sessionFile path provided by the command for continui
 
 ## Output Sanitization
 
-Before including any consulted tool's response in the output, scan the response text and redact matches for these patterns:
-
-| Pattern | Description | Replacement |
-|---------|-------------|-------------|
-| `sk-[a-zA-Z0-9_-]{20,}` | Anthropic API keys | `[REDACTED_API_KEY]` |
-| `sk-proj-[a-zA-Z0-9_-]{20,}` | OpenAI project keys | `[REDACTED_API_KEY]` |
-| `sk-ant-[a-zA-Z0-9_-]{20,}` | Anthropic API keys (ant prefix) | `[REDACTED_API_KEY]` |
-| `AIza[a-zA-Z0-9_-]{30,}` | Google API keys | `[REDACTED_API_KEY]` |
-| `ghp_[a-zA-Z0-9]{36,}` | GitHub personal access tokens | `[REDACTED_TOKEN]` |
-| `gho_[a-zA-Z0-9]{36,}` | GitHub OAuth tokens | `[REDACTED_TOKEN]` |
-| `github_pat_[a-zA-Z0-9_]{20,}` | GitHub fine-grained PATs | `[REDACTED_TOKEN]` |
-| `ANTHROPIC_API_KEY=[^\s]+` | Key assignment in env output | `ANTHROPIC_API_KEY=[REDACTED]` |
-| `OPENAI_API_KEY=[^\s]+` | Key assignment in env output | `OPENAI_API_KEY=[REDACTED]` |
-| `GOOGLE_API_KEY=[^\s]+` | Key assignment in env output | `GOOGLE_API_KEY=[REDACTED]` |
-| `GEMINI_API_KEY=[^\s]+` | Key assignment in env output | `GEMINI_API_KEY=[REDACTED]` |
-| `AKIA[A-Z0-9]{16}` | AWS access keys | `[REDACTED_AWS_KEY]` |
-| `ASIA[A-Z0-9]{16}` | AWS session tokens | `[REDACTED_AWS_KEY]` |
-| `Bearer [a-zA-Z0-9_-]{20,}` | Authorization headers | `Bearer [REDACTED]` |
-
-Apply redaction to the full response text before inserting into the result JSON. If any redaction occurs, append a note: `[WARN] Sensitive tokens were redacted from the response.`
+Apply the redaction patterns from the consult skill (`plugins/consult/skills/consult/SKILL.md`, Output Sanitization section). The skill is the canonical source for all redaction patterns.
 
 ## Critical Constraints
 

package/adapters/opencode/agents/cross-file-enhancer.md

@@ -1,4 +1,3 @@
-<!-- AUTO-GENERATED by scripts/gen-adapters.js - DO NOT EDIT -->
 ---
 name: cross-file-enhancer
 description: Analyze cross-file semantic consistency (tools, agents, rules)