minimind-notes: Instructions file for Codex

AGENTS.md

minimind-notes AGENTS.md is an instructions file for Codex, OpenCode from joyehuang/minimind-notes. It costs 597 tokens per session, scanned A, original, Apache-2.0.

Repository-specific instructions for the MiniMind Notes project, including its folders, commands, coding style, and testing guidance. MiniMind is a project containing teaching materials and machine-learning experiments.

In plain words
What is it for?
Use it when working on the documentation site, teaching modules, Python experiments, model code, datasets, or development commands in this repository.
Why use it?
It tells an agent how this repository is organized and how to build, run, and test it. This reduces guesswork when changing project files.

Instructions file for CodexOpenCode

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

This is joyehuang/minimind-notes's own configuration. It tells Codex and OpenCode how to work on minimind-notes 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 minimind-notes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to joyehuang/minimind-notes. 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/joyehuang/minimind-notes/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/joyehuang/minimind-notes

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 minimind-notes AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/joyehuang/minimind-notes/agents-md"><img src="https://agentmods.dev/badge/instructions/joyehuang/minimind-notes/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 597 This file is loaded in full into every session.
When invoked 597 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.00597 $0.00597
Opus 5.5 $0.00239 $0.00239
Sonnet 5.5 $0.00119 $0.00119
Haiku 4.5 $0.00060 $0.00060

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

Security

Grade A, and why

minimind-notes 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 · 38 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • modules/ holds the teaching modules (e.g., modules/01-foundation/01-normalization/ with teaching.md, code_guide.md, quiz.md, and experiments/).
  • docs/, index.md, and en/ contain VitePress content; site config lives in .vitepress/.
  • learning_materials/ stores runnable example scripts; docs/ and top-level learning_log.md/knowledge_base.md store notes.
  • model/, trainer/, and dataset/ mirror the MiniMind code, training scripts, and datasets used by experiments.
  • public/ and images/ host static assets used by the docs site.

Build, Test, and Development Commands

  • Use pnpm for package management in this repo.
  • pnpm install installs VitePress dependencies.
  • pnpm run docs:dev starts the local VitePress dev server.
  • pnpm run docs:build builds the static site to .vitepress/dist.
  • pnpm run docs:preview serves the built site for verification.
  • python modules/01-foundation/01-normalization/experiments/exp1_gradient_vanishing.py runs a sample experiment.
  • pip install -r requirements.txt installs Python dependencies for experiments and training scripts.

Coding Style & Naming Conventions

  • Python follows PEP 8; black is acceptable for formatting when needed.
  • Experiments should be self-contained, use fixed seeds, and include clear (often Chinese) comments.
  • Experiment filenames use exp{N}_{description}.py and store expected outputs in results/.
  • Module folders use NN-topic-name numbering for ordering (e.g., 01-normalization).
  • Markdown should use clear headings and short, instructional paragraphs.

Testing Guidelines

  • There is no formal test runner; validate changes by building docs and running relevant experiments.
  • Keep experiment outputs reproducible and commit expected results under the module results/ folder.

Commit & Pull Request Guidelines

  • Use Conventional Commit-style messages: feat:, fix:, docs:, refactor:, perf:, style:, test:, chore:, experiment: with optional scopes (e.g., fix(build): ...).
  • Keep PRs small and focused on a single feature or fix.
  • Use .github/PULL_REQUEST_TEMPLATE.md and link related issues (e.g., Closes #123).
  • Update relevant docs when behavior or experiments change, and ensure new experiments run independently.

Read the full file on GitHub · 38 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 First seen · 38 lines · 597 tokens per session scan A e15311e909f7

Subscribe to this mod's changes

minimind-notes AGENTS.md is an instructions file published in the GitHub repository joyehuang/minimind-notes (222 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 597 tokens to every session, about $0.0024 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-30.

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,581 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 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,731 tokens