mcpField
P
publish-mod

publish-mod

github.com/rehan-remadeDevelopment9.2k1.5k installsUpdated 1d ago
Repository

About publish-mod

A skill that guides mod authors through checking, packaging, documenting, versioning, and preparing a mod for publication across listed platforms. It also keeps publication decisions and final posting under the user's control.

Key features

  1. 01Lint mod files for issues
  2. 02Platform-specific packaging guidance
  3. 03README and credit checklist
  4. 04Versioning and changelog guidance
  5. 05Publication post preparation

Use cases

  1. 01Check a mod before release
  2. 02Package a mod for its target platform
  3. 03Prepare release documentation and post

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rehan-remade/universal-modder --skill publish-mod

After installing, type/publish-modin Claude Code to confirm it loaded.

Details

From the project README

Publish a mod

1. Lint

um publish check ./MyMod --game "<game install folder>"
  • FAIL: files byte-identical to game files, leaked keys (fal/Anthropic/OpenAI/GitHub/AWS), .env files.
  • WARN: decompiler fingerprints in source (FUN_/DAT_/sub_ names, "Decompiled with" headers), large engine archives, absolute user paths, a missing README, fal assets without credit.

Fix every FAIL. Resolve each WARN deliberately. For example, AoE2 data mods do ship a modified .dat, which is the platform's norm.

2. Package the way the platform expects

Platform / loaderPackage
tModLoaderBuild → .tmod; publish from the in-game Mod Sources menu (Steam Workshop)
BepInEx / Thunderstorezip with manifest.json, icon.png (256×256), README.md, plugins/<Mod>.dll; dependency strings like BepInEx-BepInExPack-5.4.2100
Nexus Modszip laid out as it installs (Data/... for Bethesda, BepInEx/plugins/..., ue4ss/Mods/..., ~mods/*.pak)
AoE2 DEthe official mod site (ageofempires.com/mods) or the in-game uploader; data mods include resources/_common/dat/...
Steam Workshopthe game's own uploader or SDK tool
MinecraftModrinth / CurseForge jar with fabric.mod.json / neoforge.mods.toml
ROM hacks / GameMakerpatches only (BPS/IPS/xdelta), never the modified game file

A Nexus mod with options gets a FOMOD installer: see the FOMOD tutorial and STEP's FOMOD guide. Nexus Mods' own modding wiki covers the rest of their site's conventions.

3. README (in the zip and on the page)

  • What it adds: bullets, a GIF or the showcase video.
  • Requirements: game version, the loader and its version, dependencies.
  • Install, uninstall and troubleshooting (where the log is).
  • Compatibility: multiplayer? Known conflicts?
  • Credits:
    • the loader and libraries;
    • references you learned from;
    • "Art/audio generated with fal (fal.ai) using " (fal_manifest.jsonl lists them);
    • honest AI disclosure (which agent and model built it).
  • License for your code (MIT/Apache is common). Your assets' terms follow the models' licenses.

4. Version and changelog

Use semver in the manifest/build file, name the supported game version, and keep a changelog. When the game updates, re-run the in-game test scene before bumping.

5. The post

  • Lead with the video: the showcase-video skill; 20-45 s, gameplay within 2-3 s.
  • Post text: the hook, what it is, the "how" credit (which agent + fal built it), a link.
  • If the video uses anyone else's footage, credit them by handle and ask first.
  • Publishing is always the user's call. Draft it, show them, and let them press the button.

Comments

Markdown supported