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 setting-up-bgs-modding-environmentgit 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/setting-up-bgs-modding-environment)<a href="https://agentmods.dev/skills/hashgraph-online/awesome-codex-plugins/setting-up-bgs-modding-environment"><img src="https://agentmods.dev/badge/skills/hashgraph-online/awesome-codex-plugins/setting-up-bgs-modding-environment.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 83 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Rogue Agent · line 24 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00125 | $0.05667 |
| Opus 5 | $0.00063 | $0.02833 |
| Sonnet 5 | $0.00025 | $0.01133 |
| Haiku 4.5 | $0.00013 | $0.00567 |
Grade B, and why
setting-up-bgs-modding-environment scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Codex**: append to `~/.codex/config.toml`: How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting Up the BGS Modding Environment
This is the first-run bootstrap. Use it when:
- The user installed
bgs-modding-superpowersand this is the first conversation in their project directory. - A new modpack project is being set up from scratch.
- MO2 path is not yet known to the agent.
- The user explicitly asks to "set up", "install", "bootstrap", "configure", or "initialize" the BGS modding environment.
- A subsequent skill (e.g.,
xedit-automation) finds the environment incomplete and routes back here.
Hard guardrails
- Do NOT install MO2 yourself by default. The default path is to detect MO2 and, if absent, guide the human user to install it themselves. Agent-driven install requires explicit user consent ("yes, install MO2 for me").
- Never write into the user's vanilla game install (e.g.,
<Steam>/steamapps/common/<Game>/Data/). All overlays go through MO2. - Treat the user's existing MO2 profile as canonical. Do not silently mutate
profiles/<Profile>/plugins.txt,modlist.txt, INIs, or load order. - Pause and surface state before each install action. The user should always know which MO2 root, which profile, and which file is about to be touched before it happens.
- MO2 must run visibly. Never start MO2 in any background / hidden mode.
The human owner needs to see and interact with the MO2 GUI. The launch helper
scripts/start-mo2.ps1enforces this and surfaces "zombie" MO2 processes (running but no window) so they can be cleaned up before a fresh start.
What the control plane actually is
The "MO2 control plane" we deploy in step 4 is a Python MO2 plugin plus a PowerShell broker:
tools/mo2-control-plane/live-bridge/mo2_agent_control.py— the actual MO2 plugin. When MO2 loads it, the plugin opens a named pipe and starts publishing bootstrap runtime files. This is what the agent harness talks to.tools/mo2-control-plane/broker/— PowerShell IPC client used byxedit-client.ps1. Runs from the plugin checkout; no install step.
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.
- 8d ago First seen · 479 lines · 125 tokens per session scan B d7c3f5240880
setting-up-bgs-modding-environment is a skill published in the GitHub repository hashgraph-online/awesome-codex-plugins (947 stars, last pushed yesterday), licensed Apache-2.0. It adds 125 tokens to every session and 5,667 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
steam-publish
Publish or update a game on Steam with Steamworks and SteamPipe: configure depots and packages, upload builds with steamcmd, set a build live on a branch, and run the release checklists. Use for Steam publishing, appbuild.vdf/steamcmd uploads, depots, beta branches, or a store page release.
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…
save-systems
Design save/load for game state — choosing what to serialize, file formats, save slots, atomic crash-safe writes, schema versioning and migration, and autosave. Engine-neutral. Use when the user mentions save system, save/load, game state persistence, save slots, autosave, save file corruption, or migrating old saves…
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…