devstack: Instructions file for Codex

AGENTS.md

devstack AGENTS.md is an instructions file for Codex, OpenCode from MartinKuhne/devstack. It costs 483 tokens per session, scanned A, original, MIT.

A set of AGENTS.md instructions for software work, covering task scope, planning, quality checks, libraries, and commits.

In plain words
What is it for?
Planning implementation tasks, checking dependencies and risks, running quality gates, managing todos, choosing libraries, and preparing a summary commit.
Why use it?
It gives an agent a defined development process and requires build, test, and lint checks before work is considered complete.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/martinkuhne/devstack/agents-md"><img src="https://agentmods.dev/badge/instructions/martinkuhne/devstack/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 483 This file is loaded in full into every session.
When invoked 483 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.00483 $0.00483
Opus 5.5 $0.00193 $0.00193
Sonnet 5.5 $0.00097 $0.00097
Haiku 4.5 $0.00048 $0.00048

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

Security

Grade A, and why

devstack 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 2mo 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 · 51 lines

How it starts

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

Agent Principles

Scope

Work only on the item described in the prompt. Do not modify unrelated code or create unrelated commits.

Development process

  • Check the quality gates before beginning work. If there are compilation errors or tests fail, repair the tests before beginning work (unless instructed to pause tests). You are allowed to disable tests that test functionality that is no longer a requirement. If substantial test changes were needed, commit the changes and exit.
  • Create a detailed plan and decompose implementations steps into units of work that can be done by an AI agent in less than 20 minutes
  • Specify dependencies, test impact, architecture changes, risk
  • Specify complexity on a scale of 1 to 10
  • Create todos
  • Execute the plan
  • Check that all quality gates have passed
  • Create a commit message with a summary of changes and commit

Quality Gates

All quality gates must pass before marking an item done and committing the changes, unless instructed to pause testing

  • Build succeeds
  • Unit tests pass
  • No new lint errors or warnings

Libraries

  • Prefer libraries over re-inventing the wheel
  • Libraries must be under a permissive license and have no licensing cost
  • Use the latest stable version applicable to the current framework version and other libraries which are already in use
  • Always research the correct usage for the current version, using context7 or web search

Commits

  • One focused commit per work item
  • Write a clear commit message describing what changed and why
  • Do not commit unrelated changes

Code quality

  • One class per file
  • All public and internal methods have a brief description
  • Follow SOLID principles
  • Say it once
  • Do not put Client IDs and any passwords and secrets in the code
  • Use immutable data structures, pure and honest functions

For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan

Read the full file on GitHub · 51 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. 2mo ago First seen · 51 lines · 483 tokens per session scan A 6eb6e1efb351

Subscribe to this mod's changes

devstack AGENTS.md is an instructions file published in the GitHub repository MartinKuhne/devstack (2 stars, last pushed 5d ago), licensed MIT. It adds 483 tokens to every session, about $0.0019 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

devstack AGENTS.md compared with instructions from other repositories

devstack AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
devstack AGENTS.mdMartinKuhne/devstackInstructions file25d agoMITA483Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode