From 869f65eba13cc7e576d3c68e8d0ead148f363ae1 Mon Sep 17 00:00:00 2001 From: Michael Kantor <6068672+kantorcodes@users.noreply.github.com> Date: Mon, 26 Oct 2026 17:44:56 -0400 Subject: [PATCH] docs: clarify submissions from multi-plugin repositories --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643acf172..219c359b9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -124,6 +124,14 @@ Rules: - Link to the GitHub repository root when the plugin is on its default branch - If the plugin is on a non-default branch, link to `https://github.com///tree/`; validation and the centralized scan use that branch +### Multiple plugins from one source repository + +If a repository contains several independently installable Codex plugin bundles, add **one README line per plugin**, with each line linking to the same GitHub repository root. Use the plugin's own name or display name from its nested `.codex-plugin/plugin.json` so the generator can select the correct bundle. Keep the entries alphabetized in their category. + +The generator matches each README display name against the nested plugin manifests and, when the same source repository has multiple entries, mirrors the matched bundles into separate installable paths. A source `.agents/plugins/marketplace.json` does not automatically create one catalog entry per bundle. Remove any generic umbrella README entry when replacing it with separately named plugins, because it can otherwise resolve to the wrong bundle. + +For a non-default source branch, a `/tree/` URL is supported. Do **not** append `/plugins/` to that URL: the parser treats the remainder as the branch ref, not a directory selector. Each bundle still needs its own valid manifest, centralized source scan meeting the 80-point threshold, ordinary checks, and independent reviewer approval before publication. + ## Scanner requirements All plugins submitted to this list **must pass the HOL AI Plugin Scanner**.