core AGENTS.md

A project instruction file for ReactUnity that explains how to prepare release notes with Tegami, a package versioning and publishing tool.

In plain words
What is it for?
Use it when documenting fixes, preparing package version changes, or creating pending changelog files for a release.
Why use it?
It prevents release information from being written in the wrong files or without the required package and heading details.

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/reactunity/core/agents-md
Clone the repo
git clone --depth 1 https://github.com/ReactUnity/core

Made for: Codex, OpenCode.

Per session 245 This file is loaded in full into every session.
When invoked 245 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.00245 $0.00245
Opus 5 $0.00122 $0.00122
Sonnet 5 $0.00049 $0.00049
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

core 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 40 lines

What it actually says

@CLAUDE.md

Release workflow

This repository uses Tegami for versioning and publishing.

Write changelog files

Create pending changelog files under .tegami/ as YYYY-MM-DD-{hash}.md.

See the changelog format docs for details.

Example

---
packages:
  "npm:@acme/ui": patch
---

### Fix button hover state

The hover color now matches the design system.

Package references

Use package names, ids, or groups in frontmatter. For example:

  • "@acme/ui" — package name
  • "npm:@acme/ui" — package id
  • "group:acme" — every package in a group

Rules:

  • Include YAML frontmatter with packages
  • Include at least one #, ##, or ### heading in the body
  • Write user-facing release notes under each heading
  • Do not edit the publish lock file (.tegami\publish-lock.yaml) or package CHANGELOG.md files directly
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. yesterday First seen · 40 lines · 245 tokens per session scan A bccc87e27271

Subscribe to this mod's changes

core AGENTS.md is an instructions file published in the GitHub repository ReactUnity/core (893 stars, last pushed 4d ago), licensed MIT. It adds 245 tokens to every session, about $0.0012 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.

Related

Other instructions, from other repositories

unity-cli-loop AGENTS.md

AGENTS.md instructions for hatayama/unity-cli-loop, covering architecture overview, repository map, cli / unity package compatibility, project runner pin and generated skill files.

hatayama/unity-cli-loop · 3,014 tokens

unity-ui-toolkit-design-system AGENTS.md

Instructions for sinanata/unity-ui-toolkit-design-system, covering agents.md, what this project is, golden rules (do not violate), use the design system in your project and repository layout.

sinanata/unity-ui-toolkit-design-system · 3,290 tokens

unity-ui-toolkit-design-system copilot-instructions.md

Instructions for sinanata/unity-ui-toolkit-design-system: This repository follows the cross-tool AGENTS.md standard. Read /AGENTS.md for the full guide: the ds- class naming, the token rules, the load-bearing USS import order, build and preview commands, and the pull-request checklist.

sinanata/unity-ui-toolkit-design-system · 258 tokens

unity-mesh-fracture AGENTS.md

Instructions for sinanata/unity-mesh-fracture, covering agents.md, what this project is, golden rules (do not violate), wire it into your project and public api.

sinanata/unity-mesh-fracture · 2,647 tokens

Aspid.FastTools CLAUDE.md

Instructions for VPDPersonal/Aspid.FastTools, covering обзор репозитория, сборка, архитектура, карта функциональности and соглашения по коду редактора.

VPDPersonal/Aspid.FastTools · 2,948 tokens

unity-cli CLAUDE.md

Instructions for bigdra50/unity-cli, covering claude.md, project overview, commands, install globally (provides: unity-cli, u, unity commands) and run relay server standalone.

bigdra50/unity-cli · 985 tokens