Awesome Codex Plugins is a curated catalogue and marketplace of installable plugins, skills, and related resources for OpenAI Codex and ChatGPT. It helps people find, create, validate, and submit extensions for Codex workflows across its app, command-line interface, and IDE extensions. The catalogue add-ons are the plugins, skills, agents, and hooks listed or supported by this project.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hashgraph-online/awesome-codex-plugins --skill xedit-automationgit clone --depth 1 https://github.com/hashgraph-online/awesome-codex-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/xedit-automation)<a href="https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/xedit-automation"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/xedit-automation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/xedit-automation"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/xedit-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.06506 |
| Opus 5.5 | $0.00026 | $0.02602 |
| Sonnet 5.5 | $0.00013 | $0.01301 |
| Haiku 4.5 | $0.00006 | $0.00651 |
Grade A, and why
xedit-automation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xEdit Automation — Hub Skill
This skill is the always-loaded entry point for any xEdit work. It is the single source of truth for "which path do I use" and "what must I never do." Specialised task skills (e.g. xedit-conflict-audit) inherit its routing, anti-patterns, and verification discipline; they do not restate them.
Toolbox at a glance (progressive disclosure, r6-aware)
The forked xEdit daemon is best treated as a progressive-disclosure surface:
start with the small MCP intent tools, ask the live daemon which r6 capability
blocks it supports, then switch to the richer one-call patterns only when the
corresponding system.capabilities.supports.* key is present.
- Discovery & session —
xedit_session,xedit_list_capabilities. Callxedit_sessionfirst every conversation. Then callxedit_list_capabilitiesonce to see the command digest,contractVersionExpected, and r6supports.*anchors. - Reading records & conflicts —
xedit_find_record,xedit_read_record,xedit_inspect_conflicts. These are the W2 (conflict audit) backbone; branch to atomic passthrough when W2 needs an r6 response block that no intent tool exposes yet. - Atomic passthrough —
xedit_call(command, args). For any native daemon command that does not have an intent tool yet. Still runs the full pipeline (validation → state → rules → audit). Use it whenever the intent tools do not fit.
For deep reference material, query the structured BGS KB first (bgs_kb_query
/ bgs_kb_get). Deep reference records live under
knowledge/bgs-kb/packs/core/records/xedit/ (queryable via bgs_kb_query /
bgs_kb_get).
Routing doctrine (which path to use)
| Task shape | Path |
|---|---|
| High-frequency known intent (audit a conflict, read a record, run a job, write a patch) | MCP intent tool |
| Novel / debugging / free composition of native commands | MCP atomic passthrough: xedit_call(command, args) — still in harness |
| Exploratory atomic-op storm (trial-and-error, repeated read-eval, hypothesis testing) | Delegate to a read-only investigator sub-agent with this skill loaded; the sub-agent burns its own context, returns a distilled summary |
| Large formalisable bulk mutation | MCP xedit_run_script (Batch 4+) with dry-run + snapshot |
| Daemon explicitly in default (non-MCP) mode, manual debug only | Direct xedit-client.ps1 is acceptable — but ONLY when the user has explicitly accepted the risk and the daemon is not in -automation-mcp-mode |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 489 lines · 64 tokens per session scan A 180380be8bd3
xedit-automation is a skill published in the GitHub repository hashgraph-online/awesome-codex-plugins (1,373 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 6,506 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
awesome-chatgpt
Search this repository's awesome-ChatGPT-repositories list for open-source ChatGPT and LLM projects such as RAG frameworks, agents, chatbots, CLIs, prompts, and browser extensions. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, or AI development; not for editing or adding list…
awesome-chatgpt-search
Search 2500+ curated ChatGPT and LLM open-source repositories. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, RAG, agents, langchain, NLP, AI development, or any open-source AI tooling.
audio-design
Implement game audio practice — bus/mixer architecture and gain in decibels, ducking (sidechain), adaptive/dynamic music via layering and re-sequencing, SFX variation, and beat synchronization. Engine-neutral. Use when the user mentions audio mixing, audio buses, adaptive/dynamic music, ducking, SFX variation, music…
procedural-gen
Generate game content procedurally — seeded deterministic RNG, value/Perlin/ Simplex noise for terrain and heightmaps, grid dungeon generation (rooms + corridors, BSP, random walk), and weighted loot/drop tables. Engine-neutral algorithms. Use when the user mentions procedural generation, perlin/simplex noise, random…
gamemaker-gml
Best practices for GameMaker Language (GML) development, covering scripts, object events, rooms, data structures, and performance-minded game code. Use when writing GML scripts or object event code in GameMaker Studio, structuring create/step/draw events, managing rooms and instances, building state machines for…
bprr
Bulk PR reviewer for awesome-quant. Use when the user asks to review all open PRs, review unreviewed PRs, bulk review, or mentions "bprr". Reviews open PRs lacking the reviewed label and presents a summary before any merge/comment/label action.