scaffold: Instructions file for Codex

AGENTS.md

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

A set of AGENTS.md instructions for a repository that publishes reusable guidance files for coding agents.

In plain words
What is it for?
Use it when maintaining the scaffold skill pack, reviewing its skills, or adding a new skill and its supporting files.
Why use it?
It explains the repository’s purpose, directory conventions, review boundaries, and rules for adding skills. This helps contributors keep the published guidance generic and complete for people using it in other projects.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions AGENTS.md.

This is robcsaszar/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 robcsaszar/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/robcsaszar/scaffold/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/robcsaszar/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/robcsaszar/scaffold/agents-md/github.svg)](https://agentmods.dev/instructions/robcsaszar/scaffold/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/robcsaszar/scaffold/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/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/robcsaszar/scaffold/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/scaffold/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 943 This file is loaded in full into every session.
When invoked 943 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.00943 $0.00943
Opus 5.5 $0.00377 $0.00377
Sonnet 5.5 $0.00189 $0.00189
Haiku 4.5 $0.00094 $0.00094

Measured 1mo ago against content hash dc54851bd80c, 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 · 62 lines

How it starts

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

AGENTS.md

Mission

This repo publishes the scaffold skill pack: three skills for creating and reviewing the standing context files (AGENTS.md, CONTEXT.md, DESIGN.md) an AI agent reads before working on a codebase. There is no build, no tests, no runtime of its own. The deliverable is the contents of skills/*, each copied in from a source repo (Orakl) where they are used and refined, then published here for anyone to install. Changes should be judged by: would a stranger who installs one of these skills into an unrelated project get correct, generic guidance out of it?

Layout convention

  • One directory per skill under skills/<name>/, name: in frontmatter matching the directory name exactly.
  • Each skill's full directory ships as-is: SKILL.md plus any references/ it depends on. Don't split a skill across a partial copy.
  • No skill in this pack ships a scripts/ directory. If a future update adds one, add a SAFETY.md documenting it in the same change (see how ai-forge, a sibling pack, handles this).

Judgment boundaries

NEVER:

  • Never let a copied skill's content leak repo-specific references back to Orakl (or any other single source project). A published skill needs to read as generic guidance, not one project's internal notes.
  • Never remove a skill without asking first: this repo's whole value is the stable set of three, and removing one is a breaking change for anyone who installed it.

ASK:

  • Ask before changing the license or copyright holder.
  • Ask before adding a fourth skill that doesn't fit the "standing context file" shape the other three share.

ALWAYS:

  • When re-syncing a skill from its source, re-run the orakl-leakage grep (grep -rni "orakl" across skills/) before publishing, and flag any hits rather than silently editing them out.
  • When adding, removing, or renaming a skill: update the table in README.md in the same change.

Adding a skill

  1. Copy the full skill directory from its source, not just SKILL.md.
  2. Grep the copy for source-repo-specific leakage (project name, absolute paths) before publishing.
  3. Add a row to the table in README.md.
  4. Decide whether it ships a scripts/ directory; if so, add SAFETY.md describing what the script does.

Read the full file on GitHub · 62 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 · +29 lines · +418 tokens per session dc54851bd80c
  2. 2mo ago First seen · 33 lines · 525 tokens per session scan A f7e21a546f2a

Subscribe to this mod's changes

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