agentleFS
Fixed-SeedFixed-Seed/game-changer/skills/publish-mod/SKILL.md

publish-mod

Skill8 starsChanged 36 days agoMITView on GitHub

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.

  • Reads credentials

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use semver in the manifest/build file, name the supported game version, and keep a changelog.

    line 44
  2. Common:

    If the video uses anyone else's footage, credit them by handle and ask first.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publish a mod

1. Lint

fsgc publish check ./MyMod --game "<game install folder>"
  • FAIL: files byte-identical to game files, leaked keys (FixedSeed/Stripe/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, FixedSeed 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

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 FixedSeed (fixedseed.com) using <models>" (fixedseed_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 + FixedSeed 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.