i-m-senior-developer: Instructions file for Codex

AGENTS.md

i-m-senior-developer AGENTS.md is an instructions file for Codex, OpenCode from spumer/i-m-senior-developer. It costs 873 tokens per session, scanned A, original, MIT.

Project instructions for deciding when automated tests are justified and what they should verify. They cover tests for code behavior, command results, file formats, prompts, and reproduced bugs.

In plain words
What is it for?
Use them to choose test cases, apply test-driven development (writing tests before implementation), and check commands, parsers, schemas, manifests, prompts, and bug fixes.
Why use it?
They help developers avoid writing tests that do not prove a specific observable rule, while still requiring tests for behavior that can be checked reliably.

Instructions file for CodexOpenCode

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

This is spumer/i-m-senior-developer's own configuration. It tells Codex and OpenCode how to work on i-m-senior-developer 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 i-m-senior-developer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to spumer/i-m-senior-developer. 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/spumer/i-m-senior-developer/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/spumer/i-m-senior-developer

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 i-m-senior-developer AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/spumer/i-m-senior-developer/agents-md"><img src="https://agentmods.dev/badge/instructions/spumer/i-m-senior-developer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 873 This file is loaded in full into every session.
When invoked 873 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.00873 $0.00873
Opus 5.5 $0.00349 $0.00349
Sonnet 5.5 $0.00175 $0.00175
Haiku 4.5 $0.00087 $0.00087

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

Security

Grade A, and why

i-m-senior-developer 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 · 81 lines

How it starts

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

Правила работы агентов

Какие тесты писать

Автоматический тест проверяет наблюдаемое поведение или машинный контракт. Перед написанием теста ответь на четыре вопроса:

  1. Какой контракт должен сохраняться?
  2. Какое действие или входные данные запускают проверяемое поведение?
  3. Какой результат можно наблюдать снаружи?
  4. Какая ошибочная реализация должна привести к падению теста?

Если на эти вопросы нет конкретных ответов, автоматический тест не обоснован. Требование TDD не служит поводом придумывать проверку, которая не доказывает нужное свойство.

Автоматические тесты нужны для

  • исполняемого поведения функций, команд и хуков;
  • кодов возврата, вывода, ошибок и побочных эффектов команд и хуков;
  • парсеров, схем, форматов файлов и манифестов, которые читает программа;
  • выбора, сборки и маршрутизации промптов, если эти действия выполняет код и их результат можно проверить детерминированно;
  • найденного бага: тест воспроизводит ошибку до исправления и проходит после него;
  • инварианта, нарушение которого можно получить на минимальном примере или мутацией проверяемой реализации.

Точная строка может быть контрактом только тогда, когда внешний потребитель действительно зависит от неё: например, это ключ протокола или обязательный машиночитаемый заголовок.

Не писать тесты, которые

  • ищут слова или фразы в промпте как замену проверке его смысла;
  • проверяют, что одна формулировка скопирована во все справочные файлы;
  • закрепляют точный текст документа, если текст не является внешним контрактом;
  • используют snapshot большого фрагмента прозы только ради прохождения TDD;
  • проходят после замены полезного текста бессмыслицей с теми же маркерами;
  • подтверждают лишь наличие файла, ссылки или раздела, которые программа не читает.

Пример необоснованного теста:

assert "холодное чтение" in skill_text

Он обнаруживает удаление слов, но не отличает рабочий промпт от бессмысленного. Такой тест не доказывает заявленное поведение.

Как проверять промпты и документы

Read the full file on GitHub · 81 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 First seen · 81 lines · 873 tokens per session scan A d3a4ed12aaad

Subscribe to this mod's changes

i-m-senior-developer AGENTS.md is an instructions file published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 3d ago), licensed MIT. It adds 873 tokens to every session, about $0.0035 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,257 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 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