Skip to content

Examples

Britakee edited this page Jul 24, 2026 · 1 revision

Usage Examples

These assume you've enabled at least modrinth,curseforge,git,knowledge (see Getting Started).

1. Find a mod, download it with its dependencies

Prompt: "Find Create for NeoForge 1.21.1 on Modrinth and download it with its dependencies into run/neoforge-1.21.1/mods"

The agent resolves this to roughly:

modrinth_search(query="Create", facets=[["project_type:mod"],["versions:1.21.1"],["categories:neoforge"]])
modrinth_download_with_dependencies(
  project_id="<create's project id from search>",
  game_version="1.21.1",
  loader="neoforge",
  output_dir="run/neoforge-1.21.1/mods"
)

This resolves the newest matching version, downloads it, reads its dependencies list, and recursively downloads every required dependency (e.g. Registrate, Flywheel) into the same folder - one call instead of manually chasing each dependency.

2. Check if anything installed is out of date

Prompt: "Check if create-6.0.4.jar in my mods folder has an update for 1.21.1 neoforge"

modrinth_check_for_update(
  file_path="run/neoforge-1.21.1/mods/create-6.0.4.jar",
  game_versions="1.21.1",
  loaders="neoforge"
)

This hashes the local jar and asks Modrinth directly whether something newer exists - no need to already know which project that jar came from.

3. Update an installed mod in place

Prompt: "Update Create to the latest version, replacing the old jar"

modrinth_get_best_version(project_id="create", game_version="1.21.1", loader="neoforge")
modrinth_download_file(
  version_id="<resolved version id>",
  output_dir="run/neoforge-1.21.1/mods",
  replace_existing=true
)

replace_existing=true is the important part - without it, re-downloading would leave both the old and new jar installed side by side, which crashes Minecraft with a duplicate-mod-id error rather than actually updating anything.

4. Identify and clone a mod's GitHub repo into references/

Prompt: "Find the Lost Cities mod's source and clone it for 1.21.1 neoforge"

clone_source_reference(
  platform="modrinth",
  project_id="lost-cities",
  game_version="1.21.1",
  loader="neoforge",
  mod_name="lost-cities"
)

This resolves the GitHub repo from the platform listing and clones it (shallow, --depth 1) directly into references/mc_1.21.1/neoforge/lost-cities, matching the folder convention your compat-mod workflow already expects - no separate identify-then-clone-yourself step needed.

5. Bootstrap a new project from an official MDK

Prompt: "Download the NeoForge MDK for 1.21.1 as a new template"

download_mdk_template(loader="neoforge", game_version="1.21.1", target_name="my-new-mod")

Shallow-clones the official MDK into references/mdks/my-new-mod (or references/templates/ for multi-loader/stonecutter templates).

6. Look up a Minecraft class's real (deobfuscated) name and methods

Prompt: "What are the mapped methods on LivingEntity for 1.21.1?"

search_mappings(query="LivingEntity", type="class", minecraft_version="1.21.1")
get_class_details(class_name="net.minecraft.world.entity.LivingEntity")

Requires the Parchment mapping database to have been indexed already (knowledge group) - this doesn't hit a live API, it's a local lookup.

7. Ask a general modding question without cloning anything

Prompt: "Explain how mixins work"

explain_concept(concept="mixin")

Pulls from the indexed local knowledge base, not a web search - useful for concept questions that don't need a specific mod's source at all.