substrate-framework: Instructions file for Codex

AGENTS.md

substrate-framework AGENTS.md is an instructions file for Codex, OpenCode from vantasnerdan/substrate-framework. It costs 3,956 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for contributing to a scientific framework built from a sequential physics corpus, including its review and collaboration rules.

In plain words
What is it for?
Use it when working in the substrate-framework repository, especially for scientific changes, claim validation, campaign continuity, and pull-request work.
Why use it?
It explains how agents should preserve validated claims, avoid weakening useful conclusions through repeated review, and follow the project's governance process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents.

This is vantasnerdan/substrate-framework's own configuration. It tells Codex and OpenCode how to work on substrate-framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything substrate-framework configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vantasnerdan/substrate-framework. 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/vantasnerdan/substrate-framework/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/vantasnerdan/substrate-framework

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.

agentmods badge for substrate-framework AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vantasnerdan/substrate-framework/agents-md/github.svg)](https://agentmods.dev/instructions/vantasnerdan/substrate-framework/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/vantasnerdan/substrate-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/vantasnerdan/substrate-framework/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.

agentmods 80×15 button for substrate-framework AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/vantasnerdan/substrate-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/vantasnerdan/substrate-framework/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,956 This file is loaded in full into every session.
When invoked 3,956 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03956 $0.03956
Opus 5.5 $0.01582 $0.01582
Sonnet 5.5 $0.00791 $0.00791
Haiku 4.5 $0.00396 $0.00396

Measured 1mo ago against content hash c27281fbc553, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

substrate-framework 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 1mo 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 · 325 lines

How it starts

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

Substrate Framework Agent Contract

The top prize is a meaningful validated claim, fully promoted in the framework. Elite work advances the user's complete objective: a useful construction, an exposing proof, a decisive counterexample, or a better route that makes the next construction possible. Green tallies, longer ledgers, and more attempts earn no credit by themselves. The best reviewer preserves the strongest meaningful result the evidence supports.

This is the normative scientific and governance contract. AGENTS_START_HERE.md provides commands and routing.

Reward engineering: make excellent decisions desirable

Reward > gate. A gate inspects an artifact after a decision; a reward makes the awesome decision worth taking before the artifact exists. Frame each task as an achievement: name the valuable object, the elite behavior that produces it, the evidence that makes it trustworthy, and the parent question it unlocks. The glory belongs to solving that question, not satisfying a checklist.

Under RL/token pressure, the cheap substitute for success is to finish a form, weaken a statement, collect passing checks, or declare a route exhausted. Counter that pull explicitly: the great reward is the strongest true useful result and the next decisive construction. Honesty banks progress; invented success forfeits it. Rewards here express priorities, not measured model scores or changes to training weights. Put those priorities into practice by spending exploration on informative constructions and feeding their results into the next decision. Context design is a testable intervention, not a guarantee of novelty.

Standing language-editing achievement. Whenever editing this contract, a skill, or a memory template, inspect negative/gating language: “must not,” “never,” “forbidden,” “blocked,” “reject,” “gate,” “fail,” and “do not proceed.” Always replace task framing with positive rewards for elite behavior. Preserve the instruction's effect, evidence, scope, and schema fields. Necessary truth, safety, authorization, and immutable-provenance boundaries remain explicit; concealing a falsifier or deleting a required assumption is not reward framing. Retain technical verdicts such as blocked and refuted with their meaning.

Read the full file on GitHub · 325 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. 1mo ago Changed · +37 lines · +439 tokens per session c27281fbc553
  2. 1mo ago Changed · -288 lines · -9,605 tokens per session e717223d488d
  3. 1mo ago Changed · +68 lines · +3,748 tokens per session 1ec66a335c89
  4. 2mo ago First seen · 508 lines · 9,374 tokens per session scan A b1e0f521a0f8

Subscribe to this mod's changes

substrate-framework AGENTS.md is an instructions file published in the GitHub repository vantasnerdan/substrate-framework (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 3,956 tokens to every session, about $0.0158 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens