By BB-84C
Manage Bethesda Game Studios modpack curation with MCP-driven xEdit conflict audits, MO2 control plane integration, and runtime skills for environment setup, load-order editing, translation, dev-logs, and changelogs.
Use after first-run for ongoing modpack maintenance: update/install KB packs, author or register custom/mod KB packs, maintain localization glossary KBs for translator use, prune KB cache, health-check the environment, version-pin KB/tooling, or handle recurring BGS modding environment care.
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.
Use when starting ANY conversation involving Bethesda Game Studio modding, MO2, xEdit, or modpack curation. Bootstrap that loads the toolkit overview, lists available task skills, and enforces the hard rules of this plugin. Auto-injected by the OpenCode plugin's chat.messages.transform hook and by the hooks/ session-start chain in Claude Code and Codex.
Use when the user wants to translate a Bethesda Game Studios plugin (.esp/.esm/.esl) with bgs-translator/xtl, create or inspect a translation project, run LLM batch translation, generate prompt previews, or export SST/XML for xTranslator. Triggers - "translate this mod", "汉化这个 mod", "localize plugin", "build SST", "use xtl", "bgs-translator".
Use when reading, editing, or generating a Bethesda Game Studio load-order file (plugins.txt / loadorder.txt) for Fallout 4, Skyrim SE/AE/VR, Fallout 76, Starfield, or when launching xEdit with a custom plugin list. Authoritative reference for the asterisk-prefix format, official masters detection, ESL handling, and the routing rules between plugins.txt editing and xEdit daemon commands.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
An agent plugin for Bethesda Game Studio modpack curation. Installs on OpenCode, Claude Code, and Codex. Ships xEdit and knowledge-base MCP servers, an MO2 control-plane installer, and skills that walk the agent through first-run setup, conflict audit, and project documentation.
xedit MCP server — nine intent tools (xedit_session, xedit_list_capabilities, xedit_find_record, xedit_read_record, xedit_inspect_conflicts, xedit_inspect_conflicts_deep, xedit_find_records_by_pattern, xedit_create_child_record, xedit_navigate_ancestry) plus the atomic xedit_call passthrough for the native xEdit daemon command set discovered at runtime via system.capabilities. Goes through a 7-stage harness pipeline (validate → state-check → rules → forward → envelope → audit).bgs_kb MCP server — local SQLite + FTS5 knowledge-base lookup (bgs_kb_status, bgs_kb_query, bgs_kb_get) over the bundled core BGS modding KB. Works without MO2 or xEdit running.scripts/install-mo2-control-plane.ps1 into your own MO2.tools/xedit-hook-bridge/dist/.using-bgs-modding-superpowers — per-session bootstrap.setting-up-bgs-modding-environment — first-run install orchestrator (MO2 detect → control plane → optional xEdit download → dev-log / changelog init → semantic smoke test).xedit-automation + xedit-conflict-audit — the hub skill and the W2 conflict-audit workflow.writing-modpack-devlog, writing-modpack-changelog — create and maintain your modpack project's documentation at runtime.Add to the plugin array of your opencode.json:
{
"plugin": ["bgs-modding-superpowers@git+https://github.com/BB-84C/bgs-modding-superpowers.git"]
}
Full instructions: .opencode/INSTALL.md.
/plugin marketplace add BB-84C/bgs-modding-superpowers
/plugin install bgs-modding-superpowers@bgs-modding-superpowers
The bundled xedit and bgs_kb MCP servers are declared in .mcp.json and resolve via ${CLAUDE_PLUGIN_ROOT}.
Start a Codex session and paste this prompt. Your Codex agent does the install for you:
Install the bgs-modding-superpowers plugin from
https://github.com/BB-84C/bgs-modding-superpowers. Run these two commands and report back whatcodex mcp listshows afterwards:codex plugin marketplace add BB-84C/bgs-modding-superpowers codex plugin add bgs-modding-superpowers@bgs-modding-superpowersBoth
xeditandbgs_kbMCP servers should appear incodex mcp listafter install — Codex auto-imports them from the plugin's.mcp.json. If either is missing or any step fails, surface the exact error rather than working around it.
That's it. After install, restart any open Codex session so the new skills and MCP servers load.
Manual install (same two commands, run yourself):
codex plugin marketplace add BB-84C/bgs-modding-superpowers
codex plugin add bgs-modding-superpowers@bgs-modding-superpowers
Update later with:
codex plugin marketplace upgrade bgs-modding-superpowers
The repo carries the materialized plugin tree at plugins/bgs-modding-superpowers/ (Codex's marketplace schema requires the subdirectory layout). Source-of-truth files at the repo root are mirrored there by scripts/build-portable-plugin.ps1 on every release.
Start any session in your modpack project directory and ask:
Set up the BGS modding environment.
The setting-up-bgs-modding-environment skill will detect MO2, install the control plane, optionally fetch xEdit from BB-84C/TES5Edit, and initialize your dev-log + release-changelog.
You can install MO2 yourself, ask the agent to install it (explicit consent), or run in "no MO2" mode for documentation-only work.
Out of the box the xedit MCP server has no idea where your MO2 install lives. Tell it via the BGS_MO2_ROOT env var on the MCP server entry in your harness config; the value is the absolute path to the directory containing ModOrganizer.exe.
Examples:
~/.config/opencode/opencode.json, harness MCP block — set the env on the xedit server entry):npx claudepluginhub bb-84c/bgs-modding-superpowers --plugin bgs-modding-superpowersPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.