substrate-framework AGENTS.md

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

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/vantasnerdan/substrate-framework/agents-md
Clone the repo
git clone --depth 1 https://github.com/vantasnerdan/substrate-framework

Made for: Codex, OpenCode.

Per session 9,374 This file is loaded in full into every session.
When invoked 9,374 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.09374 $0.09374
Opus 5 $0.04687 $0.04687
Sonnet 5 $0.01875 $0.01875
Haiku 4.5 $0.00937 $0.00937

Measured yesterday against content hash b1e0f521a0f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

AGENTS.md · 508 lines

How it starts

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

Substrate Framework Agent Contract

This repository turns a sequential physics corpus into a self-consistent, importable, review-governed framework. Apply these rules to the entire framework. They are not a special cleanup rule for any particular late campaign.

New contributors begin with AGENTS_START_HERE.md for the operational collaboration, memory, GitNexus, skill-selection, PR, and review workflow. This file remains the normative scientific and governance contract when the two documents differ.

Goal

The sole purpose of this repository and every agent working in it is the advancement and full promotion of meaningful validated claims. Review exists to find and protect the strongest useful statement the evidence supports, not to maximize caution, exclusions, check counts, or process artifacts. Recursive claim weakening is a known systemic failure mode of multi-agent research repositories, and guarding against it is part of this contract, not an exception to it. Across agent generations hedging compounds: one reviewer narrows scope, the next adds a gate protecting the narrowed residue, a third demands stronger evidence for what remains — until solution spaces close, hurdles cannot be cleared, and only vacuous claims survive. That is not rigor; it is the objective silently replaced by process. Therefore:

  • Every acceptance gate must name the concrete failure mode it prevents and what it would have changed in a past attempt. A gate with no such pedigree is removed, not enforced. Gates accrete only through named mechanisms, never through caution alone.
  • Every attempted route terminates in exactly one route-scoped verdict: established as stated, refuted with the mechanism named, or blocked with the route's missing construction named. qualified is a waypoint, never a resting place. None of these route verdicts is automatically a verdict on its obligation or parent question. A failed route is a branch point: execute the continuation ladder in-run—method repair, reformulation or representation change, and materially different candidate generation—or demonstrate why a step is inapplicable to that route. This ladder is a minimum continuation response, not permission to block the obligation after three moves. Obligation-level no-go or blocking requires the scientific-exhaustion certificate; a finite ladder with plausible routes untried is an incomplete attempt. Single-route termination is the mirror image of recursive claim weakening and equally a systemic failure mode of this contract.
  • Freeze four distinct levels for decomposed work: the parent campaign objective, each dependency obligation or rung, each candidate route for that obligation, and each concrete attempt. A route verdict answers only its route. A rung remains active until its positive intent is established or its complete in-scope solution space is exhausted. Passing a prerequisite immediately activates the next unsatisfied parent obligation; neither successful nor failed child work inherits upward as campaign completion without the frozen closure map proving that implication.
  • Scope reduction must argue that the reduction changes what downstream work can conclude. Reduction that leaves no consumer better-informed is drift, not honesty.
  • After a claim survives two independent evidence passes, the burden shifts: further narrowing requires new contrary evidence, not new caution. When successive reviews keep shrinking a claim without such evidence, the review chain — not the claim — is failing; escalate to the user instead of narrowing again.

Read the full file on GitHub · 508 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. yesterday 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 (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 9,374 tokens to every session, about $0.0469 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-31.