Add Codex CLI plugin manifest#1625
Conversation
0xJacky
left a comment
There was a problem hiding this comment.
Thanks for the PR. I do not think this is ready to merge yet.
Findings:
-
The new scanner workflow does not run for this repository's active PR flow. The workflow only listens to pushes and pull requests targeting
main, but this PR targetsdev, and the repository's default remote HEAD isdev. Existing workflows in this checkout also targetdev. As a result, this PR currently reports no checks, so the new quality gate is not validating the manifest it introduces. -
The MCP server command in
.mcp.jsonis not usable as written. It configuresnpx 0xJacky-nginx-ui, but that package is not available on npm, and npm also rejects that package name because it contains uppercase characters. This means the plugin metadata points Codex at a command that cannot resolve. If this is intended to execute an external package later, the package name, ownership, and publishing path should be made explicit before merging.
Please update the workflow trigger to cover dev and replace the MCP command with a real, owned, installable server command, or remove the MCP server entry until it exists.
This adds a small metadata pass so the repo is easier to wire into Codex without touching runtime code.
I targeted this repo because it already exposes:
It adds
.codex-plugin/plugin.json, a starter.mcp.json, and the scanner workflow.Permissions: read-only. No secrets. No publish. No runtime changes.
If you want different command wiring or metadata values, I can adjust the branch.