Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qredence.ai/llms.txt

Use this file to discover all available pages before exploring further.

This repository ships a Codex marketplace at .agents/plugins/marketplace.json.

​
Remote install

Add the marketplace from GitHub: 
codex plugin marketplace add https://github.com/Qredence/qredence-plugins
Codex currently exposes marketplace registration in the CLI but not a codex plugin install subcommand. After adding the marketplace, install or enable the plugin you want from the Codex marketplace UI.

​
Local testing

  1. Keep each installable plugin bundle under plugins/<plugin-name>/.
  2. Register the bundle in .agents/plugins/marketplace.json.
  3. From the repo root, start codex so the repo-scoped marketplace is loaded.
The current marketplace exposes:
  • harness-engineering from ./plugins/harness-engineering
  • meta-harness from ./plugins/meta-harness
  • rlm-wiki from ./plugins/rlm-wiki
  • symphony from ./plugins/symphony

​
Local environment setup script

OpenAI’s Codex local-environment docs say setup scripts run automatically when Codex creates a new worktree, and they should only perform bootstrap work such as dependency installation or an initial build. For this repository, the setup step should stay minimal because the repo is Python-first, uses uv, and does not have a repo-level JavaScript toolchain. Use this script in Codex’s Setup script field: 
set -euo pipefail

cd "$(git rev-parse --show-toplevel)"

if ! command -v uv >/dev/null 2>&1; then
  echo "uv is required for qredence-plugins setup" >&2
  exit 1
fi

uv sync --frozen --dev
Notes:
  • uv sync --frozen --dev uses the checked-in uv.lock and installs the dev dependencies needed for the repo’s validation commands.
  • Keep environment variables in Codex settings rather than relying on export in the setup script — Codex runs setup in a separate shell session.
  • This repo does not need a build step at worktree creation time.

​
Packaging notes

  • The Codex manifest lives at .codex-plugin/plugin.json.
  • Keep manifest component paths relative to the plugin root.
  • Use skills for skill folders and mcpServers for .mcp.json.
  • Keep marketplace source.path values ./-prefixed and relative to the repo root.
  • Only plugin bundles with both manifests and .mcp.json should be registered in the marketplace. Skill-library folders under plugins/ are not enough on their own.
  • Use a policy.authentication value Codex currently accepts: ON_INSTALL or ON_USE.