setting-up-bgs-modding-environment
Use on first install of this plugin, when MO2 or xEdit is not yet detected, when starting a new modpack project, or when the user says 'set up', 'install', 'bootstrap', 'configure', or 'initialize' the BGS modding environment.
Install / Use
npx skills add hashgraph-online/awesome-codex-plugins --skill setting-up-bgs-modding-environmentInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of setting-up-bgs-modding-environment
setting-up-bgs-modding-environment scores 93/100 on our quality scale, 771st of 4,698 Development & Engineering skills we index (top 17%).
Its SKILL.md is 21 KB long, well organised into 25 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.
With 1,075 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so setting-up-bgs-modding-environment is actively maintained.
- Our last check on 2026-10-25 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
setting-up-bgs-modding-environment compared with similar skills
All 4 of these similar skills score higher than setting-up-bgs-modding-environment; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| setting-up-bgs-modding-environment (this skill)by hashgraph-online | 93 | 1.1k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install setting-up-bgs-modding-environment?
- Run
npx skills add hashgraph-online/awesome-codex-plugins --skill setting-up-bgs-modding-environment. The install tabs above show the steps for each supported agent. - Which AI agents does setting-up-bgs-modding-environment work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is setting-up-bgs-modding-environment safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is setting-up-bgs-modding-environment still maintained?
- The repository was last updated about 2 months ago, so setting-up-bgs-modding-environment is actively maintained.
Skill content
View source on GitHubname: setting-up-bgs-modding-environment description: "Use on first install of this plugin, when MO2 or xEdit is not yet detected, when starting a new modpack project, or when the user says 'set up', 'install', 'bootstrap', 'configure', or 'initialize' the BGS modding environment. Orchestrates: MO2 detection and control-plane install, MO2 visible launch, optional xEdit download from BB-84C/TES5Edit, optional bgs-translator/xtl PyPI install, dev-log and release-changelog initialization, and end-to-end semantic smoke verification."
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.
There is no C++ DLL to build or deploy at v0.1. A C++ kernel skeleton lives
under docs/internal/future-c-kernel/ as a design note for later perf-critical
paths; it is intentionally unbuilt. If a previous agent told you to "build
Mo2AgentControl.dll first" — that was wrong. The Python plugin is the
integration.
Workflow
Step 1 - Detect MO2 install
Search for ModOrganizer.exe in common locations:
$env:LOCALAPPDATA\ModOrganizer*\ModOrganizer.exeD:\ModOrganizer*\ModOrganizer.exe,E:\ModOrganizer*\ModOrganizer.exe,C:\ModOrganizer*\ModOrganizer.exe- The user's Documents folder.
- The user's Desktop / common steam-library siblings.
If exactly one MO2 install is found, propose it to the user for confirmation. If multiple, list them with paths and ask which is the target. If none, go to step 2.
Persist the confirmed install root in conversation context as MO2_Root. All
subsequent steps reference this variable.
Also surface the BGS_MO2_ROOT env-var requirement. The xedit MCP server
needs to know MO2_Root so it can resolve <MO2_Root>/tools/xEdit/xEdit.exe
and <MO2_Root>/profiles/<profile>/plugins.txt. Without it, the MCP either
falls back to a stale dev-sandbox path (silent wrong-answer on dev clones) or
errors with a "MO2 sandbox root is not configured" message (on end-user
installs). Tell the user where to set it for their harness:
- OpenCode: add to the
xeditMCP entry's env block inopencode.json:{ "mcp": { "xedit": { "env": { "BGS_MO2_ROOT": "<MO2_Root>" } } } } - Codex: append to
~/.codex/config.toml:[mcp_servers.xedit.env] BGS_MO2_ROOT = "<MO2_Root>" - Claude Code: set the env var in the shell that launches Claude Code, or
edit
<plugin-root>/.mcp.jsonto add anenvblock on thexeditentry.
After the user sets it, the user must restart their harness session so the
MCP server picks up the new env. Confirm by calling xedit_status({}) and
checking that the returned hint no longer mentions BGS_MO2_ROOT.
Per-call override is also available: xedit_start({ moRoot: "<MO2_Root>", ... }).
Useful for one-off testing, but the env-var path is what makes restarts and
subsequent sessions work without re-passing it.
Step 2 - If MO2 absent: branch the user
Surface a [BLOCKED] notice and offer THREE paths, in order of preference:
(a) Default - human install. Provide the official MO2 release URL: https://github.com/ModOrganizer2/modorganizer/releases/latest. Give the user a brief setup outline (download installer, pick an install root outside Program Files, launch once to initialize). Wait for the user to install and come back with the path.
(b) Agent-handled install (explicit user consent required). Only if the
user says something like "yes, install MO2 for me, go ahead": download the
official MO2 installer to a temp location, run it (silent install where
supported), register the resulting path as MO2_Root. Surface every step
("downloading from ...", "installing to ...", "MO2 ready at ..."). Never
proceed without the explicit verbal consent.
(c) No-MO2 mode. If the user says "I do not need MO2 for this project"
(e.g., they are writing modpack docs / planning without a runtime), record
MO2_Root = none, continue through step 3 for KB target selection, then skip to
step 9 (dev-log / changelog init). Mark that any MO2-bound or xEdit-bound work
will be unavailable until they revisit this skill.
Step 3 - First-run KB target selection and pack acquisition
Ask which target games the modpack should support. Use the exact game codes
when talking to KB tools where possible: SkyrimLE, SkyrimSE, SkyrimAE,
SkyrimVR, Fallout4, Fallout4VR, Fallout3, FalloutNV, Starfield.
The bundled bgs-kb-core pack is materialized inside the plugin tree at
plugins/bgs-modding-superpowers/knowledge/bgs-kb/packs/core/. No action is
needed for it; it appears in bgs_kb_status even before MO2 or xEdit are
configured.
Per-game packs (bgs-kb-skyrim, bgs-kb-fallout4, bgs-kb-fallout3-fnv,
bgs-kb-starfield) are published as GitHub Release artifacts on the
BB-84C/bgs-modding-superpowers repo. The KB MCP wraps the entire fetch +
sha256 verify + cache install in two tools — do not download zips by hand:
-
Map the chosen games to pack IDs:
SkyrimLE/SkyrimSE/SkyrimAE/SkyrimVR->bgs-kb-skyrimFallout4/Fallout4VR->bgs-kb-fallout4Fallout3/FalloutNV->bgs-kb-fallout3-fnvStarfield->bgs-kb-starfield
Additionally, if the user has indicated a translation/localization workflow for any of these games (intent to run
xtl batchagainst the game), add the corresponding localization pack. Today's released localization packs:Starfield+ Simplified Chinese ->bgs-l10n-starfield-zhhans(151k Bethesda-official terminology entries; RAG retrieval insidextldepends on this pack — seeusing-bgs-translator.)
These follow the same install path (
bgs_kb_check_updates->bgs_kb_install_pack) and the same on-disk cache layout as the per-game packs. Do not assume a localization pack is present just because the per-game pack is installed; checkbgs_kb_statusafter install. -
List what is available from the live release manifest:
bgs_kb_check_updates({})This reads the published
manifest-index.jsonand returns the latest{ packId, version, sha256, url, breakingChange }for every official pack. Surface the per-game-pack rows that match the chosen games before doing anything else. -
Get explicit user consent before installing each pack ("yes, install
bgs-kb-skyrim"). Pack install mutates~/.bgs-modding-superpowers/kb/packs/<packId>/<version>/(legacy%LOCALAPPDATA%/bgs-modding-superpowers/kb/packsis no longer used; the cache root is unified withxtl). -
For each consented pack:
bgs_kb_install_pack({ packId: "bgs-kb-skyrim", version: "<from check_updates>", dryRun: true })Verify the dry-run reports the expected version + sha256, then re-run without
dryRunto actually install. The MCP downloads from the official release URL, verifies sha256, and lays the pack out in the versioned cache. -
If
bgs_kb_check_updatesreturns an empty or partial list for a game the user wanted (network failure, release not yet published), say so and continue with the bundled core pack. Do not improvise a download URL oriwrinto the cache by hand.
Smoke test after selection / install:
bgs_kb_status({})
bgs_kb_query({ query: "plugins", games: ["<chosen-game>"], maxResults: 3 })
Success criterion: bgs_kb_status lists every pack that was just installed
plus bgs-kb-core, and bgs_kb_query returns at least one hit. If only the
core pack is available, a core-pack hit is enough for first-run.
For routine update / prune / version-pinning work after first-run, route to
maintaining-modding-environments — it documents the full ongoing-care flow
on top of the same two MCP tools.
Step 3A - Install or verify xtl for AI translation workflows
If the user plans to translate mods, or a downstream workflow routes into
using-bgs-translator, make sure the standalone translator CLI is available.
xtl is distributed on PyPI as the bgs-translator package; do not assume it
is present in a fresh machine just because this plugin is installed.
Start with a readback:
# Check whether the translator CLI is already installed and can report capabilities.
xtl version
If xtl is missing, choose one install path:
# Preferred user-level CLI install when pipx is available.
pipx install bgs-translator==0.9.0rc1
# Fallback when pipx is unavailable, or when the user wants xtl inside the active Python environment.
py -3.12 -m pip install bgs-translator==0.9.0rc1
For a future stable release, the same commands can omit the exact prerelease
pin, for example pipx install bgs-translator or
py -3.12 -m pip install bgs-translator. Do not use broad
pip install --pre bgs-translator as routine setup; it can opt unrelated
dependencies into prerelease builds. Pin an exact release candidate only when
that exact version is the intended runtime.
Verify after install:
# Confirm xtl is on PATH and exposes the expected command surface.
xtl version
# Inspect the top-level help before choosing subcommands or options.
xtl --help
# Inspect provider-profile options instead of assuming a single SDK kind.
xtl profile add --help
# Inspect GUI launch options if the user wants the web translator.
xtl gui --help
If xtl version fails after a pipx install, surface the pipx PATH warning and
ask the user to reopen the shell/session, then retry. Once it passes, route
actual translation work to using-bgs-translator; this setup skill only
installs and smoke-checks the CLI.
Step 4 - Install the MO2 control plane (Python + broker)
Once MO2_Root is known (path a or b), deploy the Python plugin:
& "<plugin-root>/scripts/install-mo2-control-plane.ps1" -MO2Root "<MO2_Root>"
This deploys:
tools/mo2-control-plane/live-bridge/mo2_agent_control.py-><MO2_Root>/plugins/- The
Mo2AgentControl/support tree -><MO2_Root>/plugins/ - `ModOrganizer.ini lock_gui=fa
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
