packwiz-url-add

name	packwiz-url-add
description	Adds non-CurseForge and non-Modrinth direct-download files to a packwiz modpack. Use for private mods, forks, custom 1.12.2 Forge JARs, or stable direct URLs that packwiz cannot manage through platform commands.

Packwiz URL Add

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 SHOULD use this when a file has a stable direct download URL and no better platform-specific packwiz command applies.

Workflow

1. The agent MUST work from the pack root containing pack.toml.
2. The agent MUST add the external file:

packwiz url add "<display name>" "<direct-download-url>"

3. The agent SHOULD use --meta-name <file-name.pw.toml> when the generated metadata filename would be unclear.
4. The agent SHOULD run packwiz list -v and inspect the generated .pw.toml for name, filename, side, URL, and hash.
5. The agent MUST run packwiz refresh after any manual edits.

Guardrails

• The agent MUST NOT use packwiz url add for CurseForge or Modrinth files unless the user explicitly wants to bypass platform metadata; platform commands preserve update metadata and dependencies.
• The agent MUST use --force only when intentionally bypassing a supported platform URL.
• For private files without a stable URL, the agent SHOULD place the file directly in the pack and run packwiz refresh; Git LFS MAY be used for large binaries.