[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6C159FWW5HP2YFAMWNC7M":3,"skill-same:01M7F6C159FWW5HP2YFAMWNC7M":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M7F6C159FWW5HP2YFAMWNC7M","unified-ai-gateway",null,"Operate and evaluate Unified AI System through nine governed MCP tools, including provider-free prompt enhancement, while preserving fake-provider, authorization, and evidence boundaries.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Funified-ai-gateway\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: unified-ai-gateway\ndescription: Operate and evaluate Unified AI System through nine governed MCP tools, including provider-free prompt enhancement, while preserving fake-provider, authorization, and evidence boundaries.\ncategory: ai-ml\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Ftree\u002Fmaster\u002Fskills\u002Funified-ai-gateway\nsource_repo: happy520ai\u002Funified-ai-system\nsource_type: official\ndate_added: \"2026-08-01\"\nauthor: happy520ai\ntags: [ai-gateway, codex, mcp, self-hosted, governance]\ntools: [codex]\nlicense: Apache-2.0\nlicense_source: https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002FLICENSE\n---\n\n# Unified AI Gateway\n\n## Overview\n\nUse the official `unified-ai-system` MCP server to inspect and exercise a local\nAI gateway without provider credentials. This skill file provides operating\nguidance; it does not install the server or change Codex configuration by\nitself. The official Codex plugin bundles the MCP definition, while skill-only\ninstallations require the manual setup below.\n\n## Version Note\n\nThe current public project release and latest reviewed immutable MCP image are\nboth `v0.4.9`. The inspection procedure below pins its recorded digests; those\nvalues must not be silently replaced with a mutable tag. Use only the reviewed,\ndigest-pinned procedure below, including for a provider-free demo. A new content\nreview is required before changing this pinned procedure.\n\n## Prerequisites And Setup\n\n1. Confirm that Codex CLI and Docker are installed and Docker is running.\n2. If the nine tools are already visible, skip setup and do not register a\n   duplicate server.\n3. Explain the first stage: it downloads one reviewed platform from the\n   immutable `0.4.9` multi-platform index into Docker's cache, inspects its\n   metadata and layer history, creates but never starts a temporary container,\n   exports its root filesystem, removes that temporary container, and writes an\n   inspection inventory to a temporary directory. The reviewed platforms are\n   linux\u002Famd64 and linux\u002Farm64. Obtain explicit user approval for those download\n   and inspection changes only.\n4. After that first approval, pull the reviewed platform manifest and complete\n   the inspection. Do not execute the image or register it yet:\n\n```bash\nIMAGE='ghcr.io\u002Fhappy520ai\u002Funified-ai-system\u002Fmcp-server@sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3'\nPLATFORM='linux\u002Famd64' # Use linux\u002Farm64 only on a reviewed ARM64 engine.\nREVIEW_DIR=\"$(mktemp -d)\"\n\ndocker pull --platform \"$PLATFORM\" \"$IMAGE\"\ndocker image inspect \"$IMAGE\" --format 'Id={{.Id}} OS={{.Os}} Architecture={{.Architecture}} User={{json .Config.User}} Entrypoint={{json .Config.Entrypoint}} Cmd={{json .Config.Cmd}} Labels={{json .Config.Labels}}'\ndocker image history --no-trunc \"$IMAGE\" > \"$REVIEW_DIR\u002Fimage-history.txt\"\n\nREVIEW_CONTAINER=\"$(docker create --platform \"$PLATFORM\" --pull never --entrypoint \u002Fbin\u002Ftrue \"$IMAGE\")\"\ndocker export --output \"$REVIEW_DIR\u002Frootfs.tar\" \"$REVIEW_CONTAINER\"\ndocker rm \"$REVIEW_CONTAINER\"\n\ntar -tf \"$REVIEW_DIR\u002Frootfs.tar\" > \"$REVIEW_DIR\u002Frootfs-files.txt\"\nmkdir -p \"$REVIEW_DIR\u002Frootfs\"\ntar --same-permissions -xf \"$REVIEW_DIR\u002Frootfs.tar\" -C \"$REVIEW_DIR\u002Frootfs\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -print > \"$REVIEW_DIR\u002Fapp-files.txt\"\n: > \"$REVIEW_DIR\u002Fapp-links.txt\"\nwhile IFS= read -r -d '' APP_LINK; do\n  ls -ld -- \"$APP_LINK\" >> \"$REVIEW_DIR\u002Fapp-links.txt\"\ndone \u003C \u003C(find \"$REVIEW_DIR\u002Frootfs\u002Fapp\" \\( -type l -o -type f -links +1 \\) -print0)\n: > \"$REVIEW_DIR\u002Fnative-binaries.sha256\"\nwhile IFS= read -r -d '' NATIVE_BINARY; do\n  sha256sum -- \"$NATIVE_BINARY\" >> \"$REVIEW_DIR\u002Fnative-binaries.sha256\"\ndone \u003C \u003C(find \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -name '*.node' -print0)\nfind \"$REVIEW_DIR\u002Frootfs\" -type f \\( -perm -0100 -o -perm -0010 -o -perm -0001 \\) -print > \"$REVIEW_DIR\u002Fexecutable-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\" -type f \\( -perm -4000 -o -perm -2000 \\) -print > \"$REVIEW_DIR\u002Fsuid-sgid-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f \\( -name '.env' -o -name '.env.*' -o -name '*.pem' -o -name '*.key' -o -name '*.p12' -o -name '*.pfx' -o -path '*\u002F.ssh\u002Fid_*' \\) -print > \"$REVIEW_DIR\u002Fcredential-like-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -name 'package.json' \\\n  -exec grep -nHE '\"(preinstall|install|postinstall|prepare|prepack|postpack)\"' -- {} + \\\n  > \"$REVIEW_DIR\u002Flifecycle-hooks.txt\"\nfind \\\n  \"$REVIEW_DIR\u002Frootfs\u002Fapp\u002Fpackages\u002Fmcp-server\u002Fsrc\" \\\n  \"$REVIEW_DIR\u002Frootfs\u002Fapp\u002Fpackages\u002Fshared-sdk\u002Fsrc\" \\\n  -type f \\\n  -exec grep -nHE 'child_process|spawn\\(|fetch\\(|AI_GATEWAY_MCP_URL|process\\.env|writeFile|appendFile|unlink|rm\\(' -- {} + \\\n  > \"$REVIEW_DIR\u002Fruntime-sensitive-code.txt\"\n```\n\nIf `sha256sum` is unavailable, use the platform's SHA-256 utility and preserve\nthe same report. Keep the review directory until the report is accepted; its\ndeletion is another filesystem change and requires approval for the exact path.\n\n5. Read every generated inventory and report the inspection before proceeding.\n   Compare it with the versioned\n   [image content review](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002F8561ec5c9e9d1ecf499c1be5aba0ba3720219074\u002Fdocs\u002Fsecurity\u002Fmcp-image-review-0.4.9.md).\n   Require OCI index digest\n   `sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3`.\n   For linux\u002Famd64, require manifest digest\n   `sha256:ff6cf988b01d5fb2e97aabe8e952f6a303dcffe650df5b4dcb0ba3d51ee88c06`\n   and config digest\n   `sha256:0c2c0c7b9c7fb7ca24c73d9a903bcf719b079a0b285a3a3269ee3ae059905e97`.\n   For linux\u002Farm64, require manifest digest\n   `sha256:90318b9e373820f863c1c1addc759be4b5ce186f2ecb6232ee502fad7c6613de`\n   and config digest\n   `sha256:c2047eb63fdc42bcb16d53fca17d78a4a6fb355cf6320b9aa6688e594371054f`.\n   Require source `https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system`, revision\n   `342a47313927870bcc696be13c9e5fb922062dac`, version `0.4.9`, license\n   `Apache-2.0`, entrypoint `docker-entrypoint.sh`, and command\n   `node packages\u002Fmcp-server\u002Fsrc\u002Findex.js`.\n\n   Report these reviewed risks explicitly: the image uses the default root\n   user; includes Debian shell\u002Fpackage utilities and 11 base-image SUID\u002FSGID\n   files; contains 522 internal pnpm links, three native Node binaries, and eight\n   lifecycle-hook declarations; and starts a child gateway with loopback HTTP.\n   The optional `AI_GATEWAY_MCP_URL` can make an HTTP or HTTPS connection only\n   when explicitly passed. The registered command below passes no host files,\n   environment variables, or ports and disables container networking. Stop on\n   any mismatch, unexpected link, credential-like file, native binary, hook,\n   privileged file, or sensitive-code behavior.\n6. Explain the second stage: it persists a Codex MCP configuration and permits\n   Codex to launch the inspected image in a later task. Obtain a separate\n   explicit approval for registration and activation; the download approval\n   does not carry over.\n7. After that second approval, register the reviewed platform digest with\n   pulling, container networking, Linux capabilities, and privilege escalation\n   disabled, then inspect the stored configuration:\n\n```bash\nIMAGE='ghcr.io\u002Fhappy520ai\u002Funified-ai-system\u002Fmcp-server@sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3'\nPLATFORM='linux\u002Famd64' # Match the reviewed platform inspected above.\ncodex mcp add unified-ai-system -- docker run --rm -i --pull never --platform \"$PLATFORM\" --network none --cap-drop ALL --security-opt no-new-privileges \"$IMAGE\"\ncodex mcp get unified-ai-system --json\n```\n\n8. Restart Codex or open a new task, then use `\u002Fmcp verbose` to confirm that all\n   nine tools are available. Remove the registration when it is no longer\n   wanted:\n\n```bash\ncodex mcp remove unified-ai-system\n```\n\nRemoving the registration does not remove the pulled image from Docker's\ncache. Treat image-cache deletion as a separate host-state change and obtain\napproval before doing it.\n\n## When to Use This Skill\n\n- Use when a user asks whether Unified AI System is healthy or ready.\n- Use when a user wants a credential-free gateway chat proof.\n- Use when a user asks about the gateway's knowledge, workflow, or workforce\n  surfaces.\n- Use when a user wants evidence from the bundled MCP tools rather than a claim\n  inferred from documentation or process exit codes.\n\nDo not use this skill for generic model comparisons, unrelated MCP servers, or\ndeploying a production gateway.\n\n## Workflow\n\n1. Confirm that the `unified-ai-system` MCP tools are available in the current\n   task. If they are absent, follow the approved setup above and wait for a\n   restarted or new task.\n2. Call `gateway_health`, then `gateway_readiness`, before attempting chat.\n3. Select the narrowest additional tool that answers the request.\n4. Report returned provider, execution mode, readiness, and blockers exactly.\n5. Separate transport success from product, production-readiness, autonomy, or\n   AGI claims.\n\n## Tool Map\n\n- `gateway_health`: managed gateway status and provider mode\n- `gateway_readiness`: chat-path readiness and blockers\n- `gateway_prompt_enhance`: local prompt structuring without a provider call\n- `gateway_chat`: deterministic credential-free chat proof\n- `knowledge_readiness`: knowledge subsystem readiness\n- `workflow_health`: workflow subsystem status\n- `workflow_actions`: available workflow actions\n- `workforce_health`: workforce subsystem status\n- `workforce_agents`: available workforce agents\n\n## Example\n\n```text\nUser: Check whether the local gateway is ready, then prove chat works safely.\n\nAgent:\n1. Call gateway_health.\n2. Call gateway_readiness.\n3. Call gateway_chat only if both results prove fake-provider mode.\n4. Report provider, model, execution mode, response, and every blocker.\n```\n\n## Safety Boundaries\n\n- Keep the credential-free local fake provider as the default.\n- Never request, read, or transmit provider credentials through this skill.\n- Do not enable or call a real provider without explicit scoped authorization.\n- Treat MCP registration, image pulls, container creation, networking, and\n  teardown as host-state changes that require informed user approval.\n- Never substitute a mutable tag, a different OCI index, or an unreviewed\n  platform manifest for the reviewed `0.4.9` identities. Keep download and\n  inspection approval separate from registration and activation approval.\n- Keep `--pull never` in the registered command. If the reviewed image is\n  absent from the local cache, fail closed and return to the first approval\n  stage.\n- Keep `--network none`, `--cap-drop ALL`, and\n  `--security-opt no-new-privileges` in the registered command.\n- Do not claim production readiness, L5 autonomy, or AGI from a healthy handshake.\n- Treat a zero exit code as transport evidence, not proof that readiness gates\n  passed.\n\n## Limitations\n\n- This skill file does not bundle the MCP server, Docker image, or Codex\n  configuration. It only operates tools supplied by the separately installed\n  official integration.\n- It does not deploy, benchmark, or certify the gateway for production use.\n- The credential-free chat tool proves only the deterministic local fake path.\n- It does not configure real providers or handle provider credentials.\n- The published MCP image requires Docker.\n- The reviewed `0.4.9` path covers linux\u002Famd64 and linux\u002Farm64. Do not activate\n  another platform image without a separate content review.\n- The image runs as the container's default root user and bundles the gateway\n  source, package-manager tooling, native dependencies, and base-image\n  SUID\u002FSGID files. The registered command drops capabilities, prevents new\n  privileges, disables networking, and leaves the image in Docker's cache.\n- Existing Codex tasks may not hot-load a newly installed MCP configuration.\n\n## Troubleshooting\n\n- If the tools are missing after approved registration, inspect\n  `codex mcp get unified-ai-system --json`, then restart Codex or start a new\n  task.\n- If readiness is blocked, report the returned blocker instead of retrying chat\n  blindly.\n- If the runtime might use a real provider, stop before chat and keep the\n  session read-only.\n\n## Additional Resources\n\n- [Unified AI System](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system)\n- [60-second Codex MCP quickstart](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002Fdocs\u002Fcodex-mcp-quickstart.md)\n- [MCP server guide](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002Fpackages\u002Fmcp-server\u002FREADME.md)\n- [MCP image content review](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002F8561ec5c9e9d1ecf499c1be5aba0ba3720219074\u002Fdocs\u002Fsecurity\u002Fmcp-image-review-0.4.9.md)\n","# Unified AI Gateway\n\n## Overview\n\nUse the official `unified-ai-system` MCP server to inspect and exercise a local\nAI gateway without provider credentials. This skill file provides operating\nguidance; it does not install the server or change Codex configuration by\nitself. The official Codex plugin bundles the MCP definition, while skill-only\ninstallations require the manual setup below.\n\n## Version Note\n\nThe current public project release and latest reviewed immutable MCP image are\nboth `v0.4.9`. The inspection procedure below pins its recorded digests; those\nvalues must not be silently replaced with a mutable tag. Use only the reviewed,\ndigest-pinned procedure below, including for a provider-free demo. A new content\nreview is required before changing this pinned procedure.\n\n## Prerequisites And Setup\n\n1. Confirm that Codex CLI and Docker are installed and Docker is running.\n2. If the nine tools are already visible, skip setup and do not register a\n   duplicate server.\n3. Explain the first stage: it downloads one reviewed platform from the\n   immutable `0.4.9` multi-platform index into Docker's cache, inspects its\n   metadata and layer history, creates but never starts a temporary container,\n   exports its root filesystem, removes that temporary container, and writes an\n   inspection inventory to a temporary directory. The reviewed platforms are\n   linux\u002Famd64 and linux\u002Farm64. Obtain explicit user approval for those download\n   and inspection changes only.\n4. After that first approval, pull the reviewed platform manifest and complete\n   the inspection. Do not execute the image or register it yet:\n\n```bash\nIMAGE='ghcr.io\u002Fhappy520ai\u002Funified-ai-system\u002Fmcp-server@sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3'\nPLATFORM='linux\u002Famd64' # Use linux\u002Farm64 only on a reviewed ARM64 engine.\nREVIEW_DIR=\"$(mktemp -d)\"\n\ndocker pull --platform \"$PLATFORM\" \"$IMAGE\"\ndocker image inspect \"$IMAGE\" --format 'Id={{.Id}} OS={{.Os}} Architecture={{.Architecture}} User={{json .Config.User}} Entrypoint={{json .Config.Entrypoint}} Cmd={{json .Config.Cmd}} Labels={{json .Config.Labels}}'\ndocker image history --no-trunc \"$IMAGE\" > \"$REVIEW_DIR\u002Fimage-history.txt\"\n\nREVIEW_CONTAINER=\"$(docker create --platform \"$PLATFORM\" --pull never --entrypoint \u002Fbin\u002Ftrue \"$IMAGE\")\"\ndocker export --output \"$REVIEW_DIR\u002Frootfs.tar\" \"$REVIEW_CONTAINER\"\ndocker rm \"$REVIEW_CONTAINER\"\n\ntar -tf \"$REVIEW_DIR\u002Frootfs.tar\" > \"$REVIEW_DIR\u002Frootfs-files.txt\"\nmkdir -p \"$REVIEW_DIR\u002Frootfs\"\ntar --same-permissions -xf \"$REVIEW_DIR\u002Frootfs.tar\" -C \"$REVIEW_DIR\u002Frootfs\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -print > \"$REVIEW_DIR\u002Fapp-files.txt\"\n: > \"$REVIEW_DIR\u002Fapp-links.txt\"\nwhile IFS= read -r -d '' APP_LINK; do\n  ls -ld -- \"$APP_LINK\" >> \"$REVIEW_DIR\u002Fapp-links.txt\"\ndone \u003C \u003C(find \"$REVIEW_DIR\u002Frootfs\u002Fapp\" \\( -type l -o -type f -links +1 \\) -print0)\n: > \"$REVIEW_DIR\u002Fnative-binaries.sha256\"\nwhile IFS= read -r -d '' NATIVE_BINARY; do\n  sha256sum -- \"$NATIVE_BINARY\" >> \"$REVIEW_DIR\u002Fnative-binaries.sha256\"\ndone \u003C \u003C(find \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -name '*.node' -print0)\nfind \"$REVIEW_DIR\u002Frootfs\" -type f \\( -perm -0100 -o -perm -0010 -o -perm -0001 \\) -print > \"$REVIEW_DIR\u002Fexecutable-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\" -type f \\( -perm -4000 -o -perm -2000 \\) -print > \"$REVIEW_DIR\u002Fsuid-sgid-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f \\( -name '.env' -o -name '.env.*' -o -name '*.pem' -o -name '*.key' -o -name '*.p12' -o -name '*.pfx' -o -path '*\u002F.ssh\u002Fid_*' \\) -print > \"$REVIEW_DIR\u002Fcredential-like-files.txt\"\nfind \"$REVIEW_DIR\u002Frootfs\u002Fapp\" -type f -name 'package.json' \\\n  -exec grep -nHE '\"(preinstall|install|postinstall|prepare|prepack|postpack)\"' -- {} + \\\n  > \"$REVIEW_DIR\u002Flifecycle-hooks.txt\"\nfind \\\n  \"$REVIEW_DIR\u002Frootfs\u002Fapp\u002Fpackages\u002Fmcp-server\u002Fsrc\" \\\n  \"$REVIEW_DIR\u002Frootfs\u002Fapp\u002Fpackages\u002Fshared-sdk\u002Fsrc\" \\\n  -type f \\\n  -exec grep -nHE 'child_process|spawn\\(|fetch\\(|AI_GATEWAY_MCP_URL|process\\.env|writeFile|appendFile|unlink|rm\\(' -- {} + \\\n  > \"$REVIEW_DIR\u002Fruntime-sensitive-code.txt\"\n```\n\nIf `sha256sum` is unavailable, use the platform's SHA-256 utility and preserve\nthe same report. Keep the review directory until the report is accepted; its\ndeletion is another filesystem change and requires approval for the exact path.\n\n5. Read every generated inventory and report the inspection before proceeding.\n   Compare it with the versioned\n   [image content review](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002F8561ec5c9e9d1ecf499c1be5aba0ba3720219074\u002Fdocs\u002Fsecurity\u002Fmcp-image-review-0.4.9.md).\n   Require OCI index digest\n   `sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3`.\n   For linux\u002Famd64, require manifest digest\n   `sha256:ff6cf988b01d5fb2e97aabe8e952f6a303dcffe650df5b4dcb0ba3d51ee88c06`\n   and config digest\n   `sha256:0c2c0c7b9c7fb7ca24c73d9a903bcf719b079a0b285a3a3269ee3ae059905e97`.\n   For linux\u002Farm64, require manifest digest\n   `sha256:90318b9e373820f863c1c1addc759be4b5ce186f2ecb6232ee502fad7c6613de`\n   and config digest\n   `sha256:c2047eb63fdc42bcb16d53fca17d78a4a6fb355cf6320b9aa6688e594371054f`.\n   Require source `https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system`, revision\n   `342a47313927870bcc696be13c9e5fb922062dac`, version `0.4.9`, license\n   `Apache-2.0`, entrypoint `docker-entrypoint.sh`, and command\n   `node packages\u002Fmcp-server\u002Fsrc\u002Findex.js`.\n\n   Report these reviewed risks explicitly: the image uses the default root\n   user; includes Debian shell\u002Fpackage utilities and 11 base-image SUID\u002FSGID\n   files; contains 522 internal pnpm links, three native Node binaries, and eight\n   lifecycle-hook declarations; and starts a child gateway with loopback HTTP.\n   The optional `AI_GATEWAY_MCP_URL` can make an HTTP or HTTPS connection only\n   when explicitly passed. The registered command below passes no host files,\n   environment variables, or ports and disables container networking. Stop on\n   any mismatch, unexpected link, credential-like file, native binary, hook,\n   privileged file, or sensitive-code behavior.\n6. Explain the second stage: it persists a Codex MCP configuration and permits\n   Codex to launch the inspected image in a later task. Obtain a separate\n   explicit approval for registration and activation; the download approval\n   does not carry over.\n7. After that second approval, register the reviewed platform digest with\n   pulling, container networking, Linux capabilities, and privilege escalation\n   disabled, then inspect the stored configuration:\n\n```bash\nIMAGE='ghcr.io\u002Fhappy520ai\u002Funified-ai-system\u002Fmcp-server@sha256:751a0d32acd2d6b1da6ad9ac67987fbd1ff36ce26b7160014d8605f18b7907b3'\nPLATFORM='linux\u002Famd64' # Match the reviewed platform inspected above.\ncodex mcp add unified-ai-system -- docker run --rm -i --pull never --platform \"$PLATFORM\" --network none --cap-drop ALL --security-opt no-new-privileges \"$IMAGE\"\ncodex mcp get unified-ai-system --json\n```\n\n8. Restart Codex or open a new task, then use `\u002Fmcp verbose` to confirm that all\n   nine tools are available. Remove the registration when it is no longer\n   wanted:\n\n```bash\ncodex mcp remove unified-ai-system\n```\n\nRemoving the registration does not remove the pulled image from Docker's\ncache. Treat image-cache deletion as a separate host-state change and obtain\napproval before doing it.\n\n## When to Use This Skill\n\n- Use when a user asks whether Unified AI System is healthy or ready.\n- Use when a user wants a credential-free gateway chat proof.\n- Use when a user asks about the gateway's knowledge, workflow, or workforce\n  surfaces.\n- Use when a user wants evidence from the bundled MCP tools rather than a claim\n  inferred from documentation or process exit codes.\n\nDo not use this skill for generic model comparisons, unrelated MCP servers, or\ndeploying a production gateway.\n\n## Workflow\n\n1. Confirm that the `unified-ai-system` MCP tools are available in the current\n   task. If they are absent, follow the approved setup above and wait for a\n   restarted or new task.\n2. Call `gateway_health`, then `gateway_readiness`, before attempting chat.\n3. Select the narrowest additional tool that answers the request.\n4. Report returned provider, execution mode, readiness, and blockers exactly.\n5. Separate transport success from product, production-readiness, autonomy, or\n   AGI claims.\n\n## Tool Map\n\n- `gateway_health`: managed gateway status and provider mode\n- `gateway_readiness`: chat-path readiness and blockers\n- `gateway_prompt_enhance`: local prompt structuring without a provider call\n- `gateway_chat`: deterministic credential-free chat proof\n- `knowledge_readiness`: knowledge subsystem readiness\n- `workflow_health`: workflow subsystem status\n- `workflow_actions`: available workflow actions\n- `workforce_health`: workforce subsystem status\n- `workforce_agents`: available workforce agents\n\n## Example\n\n```text\nUser: Check whether the local gateway is ready, then prove chat works safely.\n\nAgent:\n1. Call gateway_health.\n2. Call gateway_readiness.\n3. Call gateway_chat only if both results prove fake-provider mode.\n4. Report provider, model, execution mode, response, and every blocker.\n```\n\n## Safety Boundaries\n\n- Keep the credential-free local fake provider as the default.\n- Never request, read, or transmit provider credentials through this skill.\n- Do not enable or call a real provider without explicit scoped authorization.\n- Treat MCP registration, image pulls, container creation, networking, and\n  teardown as host-state changes that require informed user approval.\n- Never substitute a mutable tag, a different OCI index, or an unreviewed\n  platform manifest for the reviewed `0.4.9` identities. Keep download and\n  inspection approval separate from registration and activation approval.\n- Keep `--pull never` in the registered command. If the reviewed image is\n  absent from the local cache, fail closed and return to the first approval\n  stage.\n- Keep `--network none`, `--cap-drop ALL`, and\n  `--security-opt no-new-privileges` in the registered command.\n- Do not claim production readiness, L5 autonomy, or AGI from a healthy handshake.\n- Treat a zero exit code as transport evidence, not proof that readiness gates\n  passed.\n\n## Limitations\n\n- This skill file does not bundle the MCP server, Docker image, or Codex\n  configuration. It only operates tools supplied by the separately installed\n  official integration.\n- It does not deploy, benchmark, or certify the gateway for production use.\n- The credential-free chat tool proves only the deterministic local fake path.\n- It does not configure real providers or handle provider credentials.\n- The published MCP image requires Docker.\n- The reviewed `0.4.9` path covers linux\u002Famd64 and linux\u002Farm64. Do not activate\n  another platform image without a separate content review.\n- The image runs as the container's default root user and bundles the gateway\n  source, package-manager tooling, native dependencies, and base-image\n  SUID\u002FSGID files. The registered command drops capabilities, prevents new\n  privileges, disables networking, and leaves the image in Docker's cache.\n- Existing Codex tasks may not hot-load a newly installed MCP configuration.\n\n## Troubleshooting\n\n- If the tools are missing after approved registration, inspect\n  `codex mcp get unified-ai-system --json`, then restart Codex or start a new\n  task.\n- If readiness is blocked, report the returned blocker instead of retrying chat\n  blindly.\n- If the runtime might use a real provider, stop before chat and keep the\n  session read-only.\n\n## Additional Resources\n\n- [Unified AI System](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system)\n- [60-second Codex MCP quickstart](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002Fdocs\u002Fcodex-mcp-quickstart.md)\n- [MCP server guide](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002Fpackages\u002Fmcp-server\u002FREADME.md)\n- [MCP image content review](https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002F8561ec5c9e9d1ecf499c1be5aba0ba3720219074\u002Fdocs\u002Fsecurity\u002Fmcp-image-review-0.4.9.md)\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":32,"source":33,"license":15,"category":34,"date_added":35,"description":7,"source_repo":36,"source_type":37,"license_source":38},"critical",[26,27,28,29,30],"ai-gateway","codex","mcp","self-hosted","governance",[27],"happy520ai","https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Ftree\u002Fmaster\u002Fskills\u002Funified-ai-gateway","ai-ml","2026-08-01","happy520ai\u002Funified-ai-system","official","https:\u002F\u002Fgithub.com\u002Fhappy520ai\u002Funified-ai-system\u002Fblob\u002Fmaster\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Funified-ai-gateway",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill unified-ai-gateway",{"tool":53,"command":54},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill unified-ai-gateway",{"tool":56,"command":57},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill unified-ai-gateway","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Funified-ai-gateway\u002FSKILL.md",true,[],[62,70,75,82,89,96],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]