| name | detect-mods |
| description | Detects existing Minecraft mod JARs with packwiz curseforge detect and converts matching files into CurseForge metadata. Use only for CurseForge-based modpacks or when the user asks to detect CurseForge mods already present in mods/. |
Packwiz Detect Mods
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in RFC 2119.
Prerequisite
If packwiz is not available on PATH, the agent MUST install it manually from the GitHub Actions artifacts in the packwiz repository: https://github.com/packwiz/packwiz. The agent MUST verify availability with packwiz --help before running these commands.
The agent MUST use this skill only for CurseForge detection. packwiz curseforge detect fingerprints local .jar and .litemod files in mods/, queries CurseForge, creates matching .pw.toml metadata, removes matched local JARs, then refreshes the index.
Workflow
- The agent MUST work from the pack root containing
pack.toml.
- The agent MUST ensure local files to detect are under
mods/.
- The agent MUST run
packwiz curseforge detect.
- The agent MUST review unmatched or partial matches in the command output.
- The agent SHOULD run
packwiz list -v to verify detected entries.
Boundaries
- The agent MUST NOT use this for Modrinth, GitHub, direct URL, or private mods.
- The agent MUST NOT assume unmatched files are safe to delete; they SHOULD be kept or handled manually.
- If a known CurseForge file does not match, the agent SHOULD add it explicitly with
packwiz curseforge add --addon-id <project-id> --file-id <file-id> or a CurseForge file URL.
