--- name: publish-mod description: Package and release a finished game mod. Covers the pre-release lint (no game files, decompiled code or leaked keys), README and install steps, credits and AI disclosure, versioning, where to upload (Nexus Mods, Steam Workshop, Thunderstore, mod.io, GitHub releases), and the post with a video. Use when the user wants to ship, share, upload, release or post a mod. title: publish-mod canonical_url: https://skilld.dev/gh/rehan-remade/universal-modder/publish-mod last_updated: 2026-10-06T15:23:19.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install rehan-remade/universal-modder/publish-mod`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/publish-mod`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/rehan-remade/universal-modder/publish-mod) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/publish-mod`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/publish-mod --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/publish-mod --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # Publish a mod ## 1. Lint ```bash um publish check ./MyMod --game "" ``` - **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 / loader | Package | |---|---| | tModLoader | Build → `.tmod`; publish from the in-game Mod Sources menu (Steam Workshop) | | BepInEx / Thunderstore | zip with `manifest.json`, `icon.png` (256×256), `README.md`, `plugins/.dll`; dependency strings like `BepInEx-BepInExPack-5.4.2100` | | Nexus Mods | zip laid out as it installs (`Data/...` for Bethesda, `BepInEx/plugins/...`, `ue4ss/Mods/...`, `~mods/*.pak`) | | AoE2 DE | the official mod site (ageofempires.com/mods) or the in-game uploader; data mods include `resources/_common/dat/...` | | Steam Workshop | the game's own uploader or SDK tool | | Minecraft | Modrinth / CurseForge jar with `fabric.mod.json` / `neoforge.mods.toml` | | ROM hacks / GameMaker | patches only (BPS/IPS/xdelta), never the modified game file | A Nexus mod with options gets a FOMOD installer: see the [FOMOD tutorial](https://fomod-docs.readthedocs.io/en/latest/tutorial.html) and [STEP's FOMOD guide](https://stepmodifications.org/wiki/Guide:FOMOD). Nexus Mods' own [modding wiki](https://modding.wiki/en/home) 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.