scaffold: Instructions file for Claude Code

AGENTS.md

scaffold AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from victusfate/scaffold. It costs 7,929 tokens per session, scanned A, original, MIT.

Instructions for a software project that guide the agent at the start of a session and during feature work. They cover branch status, pull requests, existing planning documents, user direction, and how to begin a feature workflow.

In plain words
What is it for?
Starting feature work, checking project documents, handling branches and pull requests, and deciding how to proceed when requirements are unclear.
Why use it?
They tell the agent how to check the project’s current state and keep the user able to redirect the work. This reduces the risk of starting from outdated code or building without the needed project context.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: SessionStart hook event, but also the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

This is victusfate/scaffold's own configuration. It tells Claude Code, 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 victusfate/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/victusfate/scaffold/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/victusfate/scaffold

Made for: Claude Code, 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/victusfate/scaffold/agents-md/github.svg)](https://agentmods.dev/instructions/victusfate/scaffold/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/victusfate/scaffold/agents-md"><img src="https://agentmods.dev/badge/instructions/victusfate/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/victusfate/scaffold/agents-md"><img src="https://agentmods.dev/badge/instructions/victusfate/scaffold/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7,929 This file is loaded in full into every session.
When invoked 7,929 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.07929 $0.07929
Opus 5.5 $0.03172 $0.03172
Sonnet 5.5 $0.01586 $0.01586
Haiku 4.5 $0.00793 $0.00793

Measured 7d ago against content hash 10353218860c, 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 7d 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 · 561 lines

How it starts

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

Agent Guidelines

Harness capabilities

These instructions support Claude Code, Codex, Cursor, Antigravity (agy), and pi. Use the tools actually exposed by the current client. A named tool below is not a guarantee that it is installed. User instructions take precedence over skill defaults; infer routine choices from the repository and existing authorization.

  • Skills: /name below denotes a scaffold skill. In Codex, invoke $name or select it via /skills; read .agents/skills/<name>/SKILL.md, then its linked skills/<name>.md. Explicitly read referenced @path files relative to the containing document; do not assume Claude's import expansion.
  • Delegation: use native subagents when available. Respect client concurrency limits by batching independent reviewers. Use fresh context for review when supported; otherwise disclose the limitation and apply the criteria serially. Editing lanes use explicit git worktrees if the client lacks an isolation flag.
  • Optional tools: PR subscriptions, monitors, timers, memory, and file-delivery tools depend on the client. Use the fallbacks below; never claim an unavailable integration is active. Do not change global model, trust, or permission settings to make a workflow run.

Session and process ownership

Each session has exactly one orchestrator. Separate sessions may work concurrently, including in the same repository, but they are independent owners. Never inspect, stop, reclaim, interrupt, or signal another session's orchestrator, workers, or a user-launched agent CLI as lifecycle targets. Read-only aggregate resource checks may observe them, but process names, PIDs, terminals, queue owner labels, lease timestamps, and worktrees never establish authority over them.

Only a lifecycle controller may terminate the exact child tree it created for its current generation, and only on explicit cancel or timeout. Normal child completion must not send a cleanup signal. If ownership is ambiguous, leave the process and worktree untouched, stop conflicting dispatch, and report the conflict.

Read the full file on GitHub · 561 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. 7d ago Changed · +15 lines · +265 tokens per session 10353218860c
  2. 10d ago Changed · +48 lines · +693 tokens per session 772552fb5940
  3. 16d ago Changed · +21 lines · +347 tokens per session 4ab16cbad3c9
  4. 17d ago Changed · +1 lines · +17 tokens per session ef3ca3c777ca
  5. 24d ago Changed · +43 lines · +691 tokens per session a83d852228b5
  6. 1mo ago Changed · +14 lines · +159 tokens per session 62d90483a42b
  7. 1mo ago Changed · +29 lines · +433 tokens per session cc138b442a18
  8. 1mo ago Changed · +75 lines · +1,312 tokens per session abd980f19340
  9. 1mo ago First seen · 315 lines · 4,012 tokens per session scan A 0a237e6f38f1

Subscribe to this mod's changes

scaffold AGENTS.md is an instructions file published in the GitHub repository victusfate/scaffold (6 stars, last pushed 8d ago), licensed MIT. It adds 7,929 tokens to every session, about $0.0317 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,649 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,384 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,731 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