The repo doubles as a Claude Code marketplace (.claude-plugin/marketplace.json) and a plain git tree you can cherry-pick from. It is built to grow themed plugins and to host non-Claude formats (AGENTS.md bundles, MCP servers, Codex/Gemini/OpenCode skills) in parallel.

🧩 Plugins

Plugin	Description
`spire`	Agent orchestration system — session coordinator (Igor), domain knowledge agents (adepts), dispatching orchestrator (athanor), workpad, research tools
📖 `tome`	Knowledge layer — navigate, curate, check, handoff, init. Opt-in per project. Pairs with spire.
🧠 `g4b_ai`	(Deprecated — use `spire`) Core personal Claude Code skills
🐸 `gitea`	Gitea issue tracker integration — fetch, create, close, and comment on tickets via self-contained `uv run` scripts
🦀 `dioxus`	Per-version API reference skills for the Dioxus Rust UI library (currently 0.7+)
🕊️ `bevy`	Version-pinned skills for the Bevy Rust game engine — idiomatic 0.19 patterns plus a migration guide across breaking-change releases
📦 `project-uv`	Context-aware uv project detection — probes layout before suggesting `uv run` / `uv sync`

🚀 Install as a Claude Code marketplace

/plugin marketplace add git@git.g4b.org:dirigence/reliquary.git
/plugin install g4b_ai@reliquary

Or declaratively in a project's .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "reliquary": {
      "source": {
        "source": "git",
        "url": "git@git.g4b.org:dirigence/reliquary.git"
      }
    }
  },
  "enabledPlugins": {
    "g4b_ai@reliquary": true
  }
}

From a local clone:

/plugin marketplace add /path/to/reliquary
/plugin install g4b_ai@reliquary

Each plugin's own README documents its skills and any per-plugin install paths.

Install as a Codex marketplace

Reliquary also publishes Codex-native plugin metadata via .agents/plugins/marketplace.json and per-plugin .codex-plugin/plugin.json manifests.

From the git marketplace:

codex plugin marketplace add git@git.g4b.org:dirigence/reliquary.git
codex plugin add g4b_ai@reliquary

From a local clone:

codex plugin marketplace add /path/to/reliquary
codex plugin add g4b_ai@reliquary

Or declaratively in a project's .codex/config.toml:

[marketplaces.reliquary]
source_type = "git"
source = "git@git.g4b.org:dirigence/reliquary.git"

[plugins."g4b_ai@reliquary"]
enabled = true

From a local clone:

[marketplaces.reliquary]
source_type = "local"
source = "/path/to/reliquary"

[plugins."g4b_ai@reliquary"]
enabled = true

Codex project config is read only for trusted projects. Codex does not currently have a direct settings.local.json equivalent; use user-level ~/.codex/config.toml, profiles, or an intentionally gitignored local workflow for machine-private settings.

✂️ Grab pieces independently

A skill is just a folder containing SKILL.md. You don't need the plugin or marketplace machinery to use one:

git clone git@git.g4b.org:dirigence/reliquary.git /tmp/reliquary
mkdir -p ~/.claude/skills
cp -r /tmp/reliquary/plugins/g4b_ai/skills/workpad ~/.claude/skills/

Symlink instead of copy if you want to follow upstream:

ln -s /tmp/reliquary/plugins/g4b_ai/skills/workpad ~/.claude/skills/workpad

🗂️ Layout

reliquary/
├── .agents/
│   └── plugins/
│       └── marketplace.json       # Codex marketplace listing
├── .codex/
│   └── config.toml                # Codex project plugin setup
├── .claude/
│   └── settings.json              # Claude project plugin setup
├── .claude-plugin/
│   └── marketplace.json           # Claude marketplace listing
├── plugins/
│   ├── spire/                     # ⚗️ agent orchestration system
│   ├── tome/                      # 📖 knowledge layer (opt-in)
│   ├── g4b_ai/                    # 🧠 core skills (deprecated)
│   ├── gitea/                     # 🐸 gitea issue tracker
│   ├── dioxus/                    # 🦀 rust dioxus library reference
│   ├── bevy/                      # 🕊️ rust bevy game engine skills
│   └── project-uv/                # 📦 uv project detection
└── docs/

📐 Conventions

Commit messages use gitmoji prefixes — see docs/workpad/specs/commit-conventions.md.