{"id":19231,"plugin_id":"plugins_6a94afc8a6688191858b8a0f24f04c2c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:24.063Z","digest":"c1ea4f8b4cd191e189a6a7280c0b0b0a746cab00e1870b6498dd3e9f94314388","against":null,"payload":{"description":"Orchestrate software, repository, browser, document, automation, and system operations through one auto-routed hybrid interface. Use when the user invokes GOD MODE or asks to inspect, edit, test, build, run, automate, browse, capture, or diagnose work across cloud/mobile services and an optional local-computer bridge, including OGENIC projects and the Core-Dv1 netwalk toolkit.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":431},{"relative_path":"assets/god-mode-256.png","size_in_bytes":150452},{"relative_path":"assets/god-mode-256x258.png","size_in_bytes":88066},{"relative_path":"assets/god-mode-48.png","size_in_bytes":3140},{"relative_path":"assets/god-mode-manifest.json","size_in_bytes":1998},{"relative_path":"references/capability-matrix.md","size_in_bytes":5461}],"name":"god-mode","skill_md_contents":"---\nname: god-mode\ndescription: Orchestrate software, repository, browser, document, automation, and system operations through one auto-routed hybrid interface. Use when the user invokes GOD MODE or asks to inspect, edit, test, build, run, automate, browse, capture, or diagnose work across cloud/mobile services and an optional local-computer bridge, including OGENIC projects and the Core-Dv1 netwalk toolkit.\n---\n\n# GOD MODE\n\nOperate through one logical toolkit while selecting the best available execution surface.\n\n## Operating rules\n\n1. Classify the request as `CLOUD`, `LOCAL`, or `HYBRID`.\n2. Inspect available tools before claiming an operation is possible.\n3. Prefer a connected cloud API/MCP tool for mobile and cloud work.\n4. Use a local bridge only when the requested operation truly needs the user's computer.\n5. If no compatible surface is connected, return `LOCAL_BRIDGE_REQUIRED` or `CONNECTOR_REQUIRED` with the exact missing capability. Never simulate success.\n6. Select network direction (outbound, inbound webhook, or hybrid) automatically from the task.\n7. Read before write, preserve unrelated work, make the smallest scoped change, and verify the result.\n8. Route secret values only through an approved credential UI or secret manager — never echo them in chat.\n\n## Efficiency rules\n\n1. Read only the minimum input required for the current task.\n2. Reuse already-fetched state — do not reread unchanged files, pages, or logs.\n3. Batch independent reads and tool calls when safe.\n4. Plan internally before acting, then perform only the calls needed.\n5. Do not echo the user's input, full files, full logs, or unchanged context.\n6. Stop after the result is verified. Do not repeat checks when state has not changed.\n7. Return only important results, blockers, and next actions — expand only when detail is needed.\n8. Return only `Result`, `Blocked`, and `Next` when applicable; omit empty sections.\n\n## Deletion and Git rules\n\n1. Prefer append-only changes, new commits, reversible patches, or archive when they satisfy the request.\n2. Permit exact-target deletion after showing the impact; never broaden the target by inference or glob.\n3. For credentials, revoke or rotate first — remove the obsolete value, do not archive live secrets.\n4. Protect the default branch; use ordinary new commits for normal work.\n5. Permit scoped history cleanup only with explicit user instruction, an exact target, and a verified backup.\n6. Preserve unrelated work and verify the result after any write operation.\n\n## Surface selection\n\nUse this order unless the user names a specific surface:\n\n1. Existing first-party or connected app tool.\n2. GitHub/CI, hosted runner, n8n, or another authorized cloud execution surface.\n3. Local bridge for OS, native-app, hardware, or private-network access.\n4. A clear blocked result naming the missing connector or bridge.\n\nDo not reinterpret a cloud fallback as equivalent when it changes the target.\n\n## Unified tool families\n\n- `workspace_*`: enumerate, inspect, snapshot, and select projects.\n- `read_file`, `search_text`, `apply_patch`: inspect and patch source safely.\n- `git_status`, `git_diff`, `git_log`: review repository state and history.\n- `project_dev`, `test`, `lint`, `typecheck`, `build`: execute the project lifecycle.\n- `process_*`, `shell`, `codex_run`: run and supervise commands or delegated coding work.\n- `dom_cdp`, `accessibility`, `input_event`, `vision`, `window`: browser and UI operation.\n- `office`, `clipboard`, `file_dialog`, `screen_record`, `audio`: document and device interaction.\n- `notification`, `scheduler`, `web_fetch`, `system_info`, `health`: automation, outbound HTTP, and monitoring.\n\n## Execution workflow\n\n### Inspect\n- Resolve the exact workspace, repository, branch, page, application, or machine.\n- Check current state with the least invasive read operation.\n- Identify whether the target is cloud-accessible or local-only.\n\n### Plan\n- Map each requested action to a tool family and execution surface.\n- Select outbound, inbound, or hybrid routing automatically for the exact target.\n- Keep a concise change set; do not add unrelated providers or integrations.\n\n### Execute\n- Batch independent reads where possible.\n- Apply scoped edits; do not overwrite unrelated user changes.\n- For long-running work, surface logs and status rather than hiding the process.\n\n### Verify\n- Review diffs for code changes.\n- Run the relevant test, lint, typecheck, or build step.\n- Re-fetch cloud records after writes.\n- Report completed, skipped, and blocked items separately.\n\n## Core-Dv1 / netwalk compatibility\n\nThe GitHub source `Ogenicchocolate21debug/Core-Dv1` contains the netwalk read-only network survey toolkit.\n\n- Run network commands through its policy wrapper; never bypass the allowlist.\n- Never accept or read credential values in chat.\n- Never scan an address range without recorded user authorization.\n- Treat incomplete coverage as incomplete.\n\nGOD MODE may orchestrate netwalk but must not weaken its code-enforced guarantees.\n\n## Invocation and sharing\n\n- Explicit invocation: `Use $god-mode ...` or `@GOD MODE ...` where supported.\n- The current account can invoke the installed skill after it appears in Skills.\n- Other accounts must install the shared skill separately.\n\n## Resources\n\n- `references/capability-matrix.md`: exact cloud/local routing and fallbacks.\n- `assets/god-mode-manifest.json`: machine-readable toolkit identity and tool-family registry.\n- `assets/god-mode-256.png` and `assets/god-mode-48.png`: skill icons.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}