メニュー
Ensure KiloCode configuration parity with Claude Code and Codex across PMOVES.AI submodules. Use when auditing config consistency, checking claw scope alignment, or verifying that all three 5090 agents have equivalent capabilities.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Operate the P7 room-aware stage manager — read a room's current stage, transition a room (gated rehearsal→live via the canonical CHIT activation checklist), and observe lifecycle events on NATS. Use when claiming/transitioning a room, when the operator asks "what stage is room X in?", or when wiring a UI to reflect room transitions in real-time.
Email ingestion, triage, and review workflows for Titanmail and Gmail accounts using the Himalaya CLI and local-only processing.
Folder-triggered document processing workflows with zero-retention E2B sandbox execution for legal, research, and operations pipelines.
Legal document review, research, and case-law verification for PMOVES.AI tenant-advocacy and contract analysis workloads.
Activates n8n and Archon as the local workflow and agent orchestration layer for email, research, verification, and legal-assist jobs.
YouTube and SoundCloud channel monitoring with transcript extraction, batch processing, and routing to Hi-RAG or notebooks.
| name | kilocode-submodule-parity |
| description | Ensure KiloCode configuration parity with Claude Code and Codex across PMOVES.AI submodules. Use when auditing config consistency, checking claw scope alignment, or verifying that all three 5090 agents have equivalent capabilities. |
| keywords | ["parity","submodule","audit","claude","codex","config"] |
| version | 1.0.0 |
| category | PMOVES/KiloCode-GLM |
Configuration parity auditing between KiloCode GLM, Claude Code, and Codex on the 5090 node.
Ensure KiloCode has equivalent MCP servers, permissions, model access, and operational capabilities as Claude Code and Codex. Identify gaps and generate remediation tasks.
kilo.json vs .claude/mcp.json.kilocodemodes vs .claude/commands/)kilo.json.claude/mcp.json, .claude/settings.jsonpmoves/config/agent_registry.yamlpmoves/config/agent_signatures.yamlpmoves/configs/claws/scopes/5090.jsonpmoves/configs/claws/opencode-5090.json# Claude Code MCP servers
cat .claude/mcp.json | jq '.mcpServers | keys'
# KiloCode MCP servers
cat kilo.json | jq '.mcp | keys'
# Diff
# Missing from KiloCode: any server in Claude but not in kilo.json
# Claude deny list
cat .claude/settings.json | jq '.permissions.deny'
# KiloCode should have equivalent guardrails
cat kilo.json | jq '.permission'
# Check that primary model in kilo.json matches agent_signatures.yaml
grep -A5 "kilocode-glm" pmoves/config/agent_signatures.yaml | grep model
grep '"model"' kilo.json
# Count modes
grep "slug:" .kilocodemodes | wc -l
# Verify mode references match kilo.json instructions
grep ".kilocodemodes" kilo.json
Create a parity gap report with: