scaffold: Instructions file for Codex

AGENTS.md

scaffold AGENTS.md is an instructions file for Codex, OpenCode from zigrivers/scaffold. It costs 804 tokens per session, scanned A, original, MIT.

Project instructions for Scaffold, including its checks, release process, and rules for completing work. Scaffold is a software project with Bash and TypeScript quality gates.

In plain words
What is it for?
Use them when changing Scaffold, running its validation and tests, preparing a release, updating user-facing documentation, or publishing a version.
Why use it?
They clarify which commands to run and how releases must be prepared, reducing missed checks or incorrect publishing steps.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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

Reuse

Borrowing it

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

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 scaffold AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zigrivers/scaffold/agents-md"><img src="https://agentmods.dev/badge/instructions/zigrivers/scaffold/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 804 This file is loaded in full into every session.
When invoked 804 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.00804 $0.00804
Opus 5.5 $0.00322 $0.00322
Sonnet 5.5 $0.00161 $0.00161
Haiku 4.5 $0.00080 $0.00080

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

Security

Grade A, and why

scaffold 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 · 76 lines

How it starts

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

Agent Instructions

This repository does not use Beads for repo task tracking. Do not use the Beads CLI when working on Scaffold itself.

Quick Reference

make check            # Run bash quality gates (lint + validate + test + eval)
make check-all        # Run all quality gates (bash + TypeScript); full pre-push gate
git status -sb        # Inspect local state quickly
git pull --rebase     # Rebase onto latest remote state
git push              # Publish local commits

Autonomous Review Cycles

docs/review-standards.md is the source of truth. Keep each MMR review cycle to at most three rounds. A round-three reproducible in-scope or required-safeguard blocker may start a new bounded cycle on the same PR only after a concrete repair, focused regression proof, and the required gate pass. Review the repaired exact head from round one. No owner approval is required for this in-scope remediation. Stop immediately when the user asks to stop; otherwise use only the evidence-backed stopping conditions in the source of truth.

Do not restart for duplicate, stale, hypothetical, speculative, cosmetic, or already-dispositioned findings. Merge only after the final exact head meets the configured channel floor, required gates are green, every finding is dispositioned, and no verified blocker remains.

Scaffold Releases

When releasing Scaffold itself, follow docs/architecture/operations-runbook.md instead of the generic /scaffold:release guidance.

  • Update CHANGELOG.md and README.md when user-facing behavior, install or upgrade steps, migration instructions, or command semantics changed.
  • Merge the release-prep commit/PR to main before tagging.
  • Tag merged main as vX.Y.Z and push the tag.
  • Create the GitHub release.
  • publish.yml uses BOTH the GitHub OIDC trusted-publisher config (provenance signing only) AND the NPM_TOKEN repo secret (the actual registry PUT). As of v3.28.0 the OIDC token alone does NOT authorize the publish — if npm publish fails with auth errors, fix the NPM_TOKEN secret per docs/architecture/operations-runbook.md §4.2a, not the trusted-publisher config.
  • Verify the publish.yml and update-homebrew.yml workflows succeeded so users can update via npm update -g @zigrivers/scaffold and brew upgrade scaffold.

Read the full file on GitHub · 76 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 · +16 lines · +178 tokens per session b60aa7d741cd
  2. 2mo ago First seen · 60 lines · 626 tokens per session scan A 0d94a5a3df1f

Subscribe to this mod's changes

scaffold AGENTS.md is an instructions file published in the GitHub repository zigrivers/scaffold (6 stars, last pushed 1mo ago), licensed MIT. It adds 804 tokens to every session, about $0.0032 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