MFFS_Classic AGENTS.md

Repository instructions for MFFS Classic, a Minecraft mod that adds a Modular Force Field System to the game. They document the Minecraft and Java versions, build commands, project structure, and testing process.

In plain words
What is it for?
Use them when developing, compiling, testing, or launching the mod in a Minecraft client or server.
Why use it?
They give a coding agent the game, mod-loader, and build context needed to make compatible changes and verify them.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/builtbrokenmodding/mffs_classic/agents-md
Clone the repo
git clone --depth 1 https://github.com/BuiltBrokenModding/MFFS_Classic

Made for: Codex, OpenCode.

Per session 744 This file is loaded in full into every session.
When invoked 744 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00744 $0.00744
Opus 5 $0.00372 $0.00372
Sonnet 5 $0.00149 $0.00149
Haiku 4.5 $0.00074 $0.00074

Measured 2d ago against content hash ea9601701e87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

MFFS_Classic AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

AGENTS.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Context: MFFS Classic (Minecraft Mod)

This project is a Minecraft mod titled Modular Force Field System (MFFS) Classic

Project Stack

  • Minecraft Version: 26.1.2
  • Mod Loader: NeoForge 26.1.2.82
  • Java Version: 25 (Microsoft OpenJDK recommended for consistency with Minecraft Launcher)
  • Build System: Gradle (Kotlin DSL)
  • Mod ID: mffs
  • Main Package: dev.su5ed.mffs

Commands

Build & Development

  • ./gradlew build: Full build of the project.
  • ./gradlew assemble: Compile and package the mod jar.
  • ./gradlew runClient: Launch Minecraft client with the mod loaded.
  • ./gradlew runServer: Launch Minecraft server with the mod loaded.
  • ./gradlew runData: Run data generation to update JSON assets and data.

Testing & Verification

  • ./gradlew test: Run unit tests (if any).
  • ./gradlew downloadAssets prepareClientRun: Ensure local environment is ready for client testing.

Project Structure

  • src/main/java/dev/su5ed/mffs/: Core Java source code.
    • setup/: Registry classes (Blocks, Items, Menus, etc.) using DeferredRegister.
    • block/ / item/: Implementation of game objects.
    • network/: Networking code (Custom payloads, Packet handlers).
    • datagen/: Data generation providers.
    • MFFSMod.java: Main entry point.
  • src/main/resources/: Static assets and metadata.
    • META-INF/neoforge.mods.toml: Mod configuration and metadata.
    • assets/mffs/: Textures, models, and lang files (mostly generated).
    • data/mffs/: Recipes, loot tables, and tags (mostly generated).
  • src/generated/resources/: Output directory for data generation.

Development Guidelines

Registry & Object Initialization

  • Use DeferredRegister for all registry entries (Blocks, Items, Fluids, etc.).
  • Initialization is handled in dev.su5ed.mffs.setup.Mod* classes.
  • Ensure init(bus) is called in the MFFSMod constructor.

Data Generation (Datagen)

  • Prefer datagen over manual JSON editing.
  • Most assets (models, blockstates) and data (recipes, loot tables) are managed via dev.su5ed.mffs.datagen.
  • After changing block/item properties or adding new ones, run ./gradlew runData.

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 64 lines · 744 tokens per session scan A ea9601701e87

Subscribe to this mod's changes

MFFS_Classic AGENTS.md is an instructions file published in the GitHub repository BuiltBrokenModding/MFFS_Classic (22 stars, last pushed 8d ago), licensed MIT. It adds 744 tokens to every session, about $0.0037 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.