capshelf: Instructions file for Codex

AGENTS.md

capshelf AGENTS.md is an instructions file for Codex, OpenCode from genged/capshelf. It costs 2,861 tokens per session, scanned A, original, MIT.

A repository instruction file that gives coding agents shared project rules, including writing style, code quality, and development commands. It applies across source code, documentation, and commit messages.

In plain words
What is it for?
Use it to guide coding agents when they edit code, write documentation, answer questions, or run project commands.
Why use it?
It keeps agent work consistent with the project and makes technical writing easier to read, especially for people who are not native English speakers.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions AGENTS.md.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/genged/capshelf/agents-md"><img src="https://agentmods.dev/badge/instructions/genged/capshelf/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,861 This file is loaded in full into every session.
When invoked 2,861 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.02861 $0.02861
Opus 5.5 $0.01144 $0.01144
Sonnet 5.5 $0.00572 $0.00572
Haiku 4.5 $0.00286 $0.00286

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

Security

Grade A, and why

capshelf 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 · 205 lines

How it starts

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

AGENTS.md

This file gives coding agents the shared project context that should be true for every task in this repository. Keep it concise; prefer pointers to the living docs and source over copying long procedures here.

Writing Style

  • Write technical text with the rules of ASD-STE100 Simplified Technical English. STE is the controlled language that aerospace and defense manufacturers use for maintenance documentation. The rules exist so that a tired reader who is not a native English speaker cannot misread an instruction. They remove the usual signs of AI-generated text as a side effect: long sentences, synonym rotation, hedges, filler, and decorative clauses.
  • Write for that tired reader. Each sentence must survive one read.
  • Technical prose only, be direct
  • When the user asks a question, answer it first before making edits or running implementation commands.
  • These rules cover every document you write or edit. They are not only for conversation. They apply to docs/, README.md, release notes, commit messages, and this file.
  • This file beats the prose of an older document. Many pages under docs/ predate these rules. If a task tells you to follow an existing page, copy its structure and its section order. Do not copy its prose habits.
  • In release notes and What's New pages, use the simple past for a change that the release made: "Added --merge". Use the simple present for behavior that the software now has: "A conflict writes nothing." Do not use the imperative for a change. It reads as an instruction to the reader.
  • Before you commit a document, check the prose mechanically: count the words in each sentence outside a code fence, and grep for —, ;, and hedge words.

Project

capshelf is a Bun/TypeScript CLI for managing shared Coding Agent configuration across projects. It materializes user-owned skills, settings fragments, and future MCP config from a Git-backed data repo into consuming projects.

More info: docs/architecture.md, docs/cli.md, docs/testing.md

Read the full file on GitHub · 205 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 · +11 lines · +203 tokens per session e673763f0beb
  2. 1mo ago Changed · +15 lines · +268 tokens per session 5cb6762fb11b
  3. 1mo ago Changed · -9 lines · -101 tokens per session fc1f907c1eb9
  4. 1mo ago First seen · 188 lines · 2,491 tokens per session scan A 1d7a09a0e7d9

Subscribe to this mod's changes

capshelf AGENTS.md is an instructions file published in the GitHub repository genged/capshelf (22 stars, last pushed 6d ago), licensed MIT. It adds 2,861 tokens to every session, about $0.0114 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