Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/canon-boundary-guard-codex/llms.txt

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

Canon Boundary Guard ships as a self-contained Codex plugin. Every functional piece — the skill definition, the hook script, and the marketplace registration — lives inside a predictable directory tree rooted at the repository. Understanding the layout helps when you need to inspect, fork, or locally patch any part of the plugin.

​
Directory Tree

.agents/
└── plugins/
    └── marketplace.json
plugins/
└── canon-boundary-guard-codex/
    ├── .codex-plugin/
    │   └── plugin.json
    ├── hooks/
    │   └── hooks.json
    └── skills/
        └── canon-boundary-guard/
            ├── SKILL.md
            ├── agents/openai.yaml
            ├── references/frame.md
            └── scripts/inject_frame.py

​
File Descriptions

  • .agents/plugins/marketplace.json — exposes the plugin to Codex as a marketplace entry.
  • plugins/canon-boundary-guard-codex/.codex-plugin/plugin.json — identifies the plugin and points Codex to bundled skills and hooks.
  • plugins/canon-boundary-guard-codex/skills/canon-boundary-guard/SKILL.md — defines the full operating frame.
  • plugins/canon-boundary-guard-codex/skills/canon-boundary-guard/references/frame.md — contains the compact frame emitted by the hook script.
  • plugins/canon-boundary-guard-codex/skills/canon-boundary-guard/scripts/inject_frame.py — reads the compact frame and emits a hook payload.
  • plugins/canon-boundary-guard-codex/skills/canon-boundary-guard/agents/openai.yaml — contains Codex-facing skill metadata.
  • plugins/canon-boundary-guard-codex/hooks/hooks.json — wires the frame into PreToolUse for matched write tools when plugin hooks are enabled.

​
plugin.json

The plugin manifest at .codex-plugin/plugin.json is the root descriptor Codex reads when it loads the plugin. It declares the plugin identity, points to the skills directory and hook file, and provides display metadata including a brandColor of #536878. 
{
  "name": "canon-boundary-guard-codex",
  "version": "1.0.0",
  "description": "Codex plugin for keeping provenance and cognitive layers separate across a session.",
  "author": {
    "name": "XxYouDeaDPunKxX",
    "url": "https://github.com/XxYouDeaDPunKxX"
  },
  "homepage": "https://xxyoudeadpunkxx.github.io/canon-boundary-guard-codex/",
  "repository": "https://github.com/XxYouDeaDPunKxX/canon-boundary-guard-codex",
  "license": "CC-BY-SA-4.0",
  "keywords": [
    "codex",
    "skill",
    "plugin",
    "hooks",
    "provenance",
    "agent-control",
    "cognitive-layers",
    "ai-workflows"
  ],
  "skills": "./skills/",
  "hooks": "./hooks/hooks.json",
  "interface": {
    "displayName": "Canon Boundary Guard",
    "shortDescription": "Provenance boundary guard for Codex",
    "longDescription": "Canon Boundary Guard packages a Codex skill and optional lifecycle hook for keeping project evidence, chat context, operator instructions, working hypotheses, and model assumptions in separate cognitive layers.",
    "developerName": "XxYouDeaDPunKxX",
    "category": "Productivity",
    "capabilities": [
      "Workflow",
      "Automation"
    ],
    "websiteURL": "https://xxyoudeadpunkxx.github.io/canon-boundary-guard-codex/",
    "defaultPrompt": [
      "Use Canon Boundary Guard as the session operating frame.",
      "Use $canon-boundary-guard for provenance and cognitive-layer separation."
    ],
    "brandColor": "#536878"
  }
}
The skills field points to ./skills/ (relative to the plugin root), so Codex discovers every subdirectory under that path as a bundled skill. The hooks field points directly to ./hooks/hooks.json, which is the single hook bundle for this plugin.

Skill Reference

Full documentation for SKILL.md and the operating frame it defines.

Hook Reference

How the PreToolUse hook is configured and what it injects at write time.

Build docs developers (and LLMs) love

Get started for freeTalk to us