agentleFS
Sign inStart free
DarkTamaDarkTama/horizon-mod-skills/AGENTS.md

horizon-mod-skills

AGENTS.md1 starsChanged 17 days agoMITView on GitHub

Instructions for AI coding agents and human contributors working on this repository. horizon-mod-skills provides agent-agnostic skills and technical references teaching AI agents how to build, test, and publish native mods for Horizon using horizon-mixins. The primary skill definition lives at: - skills/horizon-native-mod/SKILL.md Detailed reference guides live in: - skills/horizon-native-mod/references/ - hook-points.md: Native hook points and helper functions. - mixins.md: horizon-mixin.toml schema, injection kinds, and helpers. - build-and-test.md: Verification pipelines and compilation constraints. - publishing.md: Package .hnmod archives and registry submission.…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Distinctive:

    Verify against code: Never invent CLI flags, TOML fields, or Rust types.

    line 24
  2. Distinctive:

    Mark unverified items: If a workflow or platform capability cannot be verified by existing logs or official code, explicitly label it as …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “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
AGENTS.md

AGENTS.md

Instructions for AI coding agents and human contributors working on this repository.

Purpose

horizon-mod-skills provides agent-agnostic skills and technical references teaching AI agents how to build, test, and publish native mods for Horizon using horizon-mixins.

Skill Location

The primary skill definition lives at:

  • skills/horizon-native-mod/SKILL.md

Detailed reference guides live in:

  • skills/horizon-native-mod/references/
    • hook-points.md: Native hook points and helper functions.
    • mixins.md: horizon-mixin.toml schema, injection kinds, and helpers.
    • build-and-test.md: Verification pipelines and compilation constraints.
    • publishing.md: Package .hnmod archives and registry submission.
    • pitfalls.md: Proven gotchas and hard lessons from real builds.

Editing Rules for Agents

  1. Verify against code: Never invent CLI flags, TOML fields, or Rust types. Confirm statements against Horizon, horizon-mixins, or the official registry repositories.
  2. Mark unverified items: If a workflow or platform capability cannot be verified by existing logs or official code, explicitly label it as unverified.
  3. No heavy builds: Agents modifying this documentation repository must not trigger full Horizon game builds. Use cargo check and manual staging tests instead.
  4. Preserve exact links: Relative markdown links must resolve within the repository. External URLs must be valid and live.
  5. Keep frontmatter valid: SKILL.md frontmatter must strictly adhere to YAML syntax with name matching the parent directory (horizon-native-mod).

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.

Check your setup, free