What is core AGENTS.md?

Baseline contribution instructions for the sima-neat core project, covering coding standards, testing, public API compatibility, documentation, and installation rules for internal runtime files.

Use it when modifying the core library, public headers, architecture or user documentation, examples, or generated NEAT runtime and plugin .so files.

It helps changes follow the project’s required review and compatibility rules, especially when public headers or internal shared-library files are changed.

How sima-neat/core configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to sima-neat/core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sima-neat/core/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/sima-neat/core

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/sima-neat/core/agents-md/github.svg)](https://agentmods.dev/instructions/sima-neat/core/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/sima-neat/core/agents-md"><img src="https://agentmods.dev/badge/instructions/sima-neat/core/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/sima-neat/core/agents-md"><img src="https://agentmods.dev/badge/instructions/sima-neat/core/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,860 This file is loaded in full into every session.

When invoked 1,860 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01860	$0.01860
Opus 5.5	$0.00744	$0.00744
Sonnet 5.5	$0.00372	$0.00372
Haiku 4.5	$0.00186	$0.00186

Measured 6d ago against content hash 930586b9cdb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 6d 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 · 128 lines

How it starts

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

Agent Guidance

This file defines baseline quality expectations for automated and human contributors.

Required standards

Follow the coding rules in docs/develop-apps/contribute/start-here/coding_standard.md.
Follow the testing rules in docs/develop-apps/contribute/build-test/test_requirements.md.
Treat public headers under include/* as stable API.

Issues and pull requests

Use the bug report template for defects and the feature request template for proposed improvements. Complete relevant sections, mark others as not applicable, and redact secrets and customer data from examples and logs.
Use the pull request template, target develop, and link completed issues with Fixes #<issue>.

API compatibility

Prefer non-breaking API changes.
Any breaking public API signature change must follow the documented process in docs/develop-apps/contribute/start-here/coding_standard.md.
PRs with breaking API changes must complete the Breaking API Change section in .github/PULL_REQUEST_TEMPLATE.md.

Documentation updates

When behavior or public API changes:

Update docs/develop-apps/contribute/start-here/architecture.md if architecture/contracts changed.
Update user-facing docs for workflow/configuration changes.
Update examples if API usage changed.

For official documentation:

Keep pages focused on the reader's task, with prerequisites, steps, and examples where useful.
Update translations required by sima-i18n*.json in the same change; refresh source hashes after verifying content alignment.
Pass localization checks and the relevant docs build, and report any validation still pending.

Runtime install contract

When rebuilding Runner or Scheduler libraries/plugins consumed by Core:

Keep /usr/lib/aarch64-linux-gnu/neat/gst-plugins and /usr/lib/aarch64-linux-gnu/neat/runtime as the canonical runtime roots.
Prefer Core's source-first build.sh workflow; it stages dependency installs before configuring Core and deploys the completed package set once.
For manual builds, build Runner then Scheduler with CMAKE_INSTALL_PREFIX=/usr and CMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu, install into a clean staging root, then select that installed package when configuring Core.
Never consume the retired Internals umbrella or its build-tree plugins as a fallback. Runner owns execution; Scheduler owns GStreamer and its installed contracts.
For AArch64 test binaries, use dk or repository DevKit wrappers rather than executing them locally.

Read the full file on GitHub · 128 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.

6d ago Changed · +63 lines · +1,007 tokens per session 930586b9cdb3
1mo ago Changed · +7 lines · +122 tokens per session ef6299a832e4
2mo ago First seen · 58 lines · 731 tokens per session scan A 17a5bdc16c28

Subscribe to this mod's changes

core AGENTS.md is an instructions file published in the GitHub repository sima-neat/core (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,860 tokens to every session, about $0.0074 per session on Opus 5.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-31.

core AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
core AGENTS.mdsima-neat/core	Instructions file	8	yesterday	Apache-2.0	A	1,860	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

core: Instructions file for Codex