configs: Instructions file for Codex

AGENTS.md

configs AGENTS.md is an instructions file for Codex, OpenCode from peerigon/configs. It costs 1,885 tokens per session, scanned A, original, MIT.

Repository-specific instructions for working on peerigon/configs, a package of shared coding, formatting, type-checking, release, editor, and agent settings.

In plain words
What is it for?
Use them when editing the repository, choosing source files, changing linting or formatting rules, updating TypeScript settings, or working with its release and agent documentation.
Why use it?
They explain which files are authoritative and which project conventions must be followed, reducing inconsistent changes across configuration packages.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/peerigon/configs/agents-md"><img src="https://agentmods.dev/badge/instructions/peerigon/configs/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,885 This file is loaded in full into every session.
When invoked 1,885 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.01885 $0.01885
Opus 5.5 $0.00754 $0.00754
Sonnet 5.5 $0.00377 $0.00377
Haiku 4.5 $0.00188 $0.00188

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

Security

Grade A, and why

configs 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 · 164 lines

How it starts

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

AGENTS.md

Purpose of this repository

@peerigon/configs is a publishable package of shared development configs and guidance:

  • ESLint presets, optional style packs, and library-specific rule sets
  • Oxlint presets (best-effort ESLint parity; opt-in alongside or instead of ESLint)
  • Prettier configuration plus plugins for import sorting, JSDoc, package.json, CSS, and Tailwind ordering
  • Oxfmt config (best-effort Prettier parity; opt-in instead of Prettier — do not run both)
  • TypeScript base and library-focused tsconfig presets
  • Semantic-release presets (including cross-publish)
  • VSCode settings reference
  • AI coding-agent rules and migration docs aligned with the same coding philosophy

The package philosophy is:

  • optimize for readability first, refactorability second, writing convenience third
  • keep formatting convention-driven and deterministic
  • keep linting focused on correctness, security, modern idioms, and a11y
  • keep type-checking strict enough for safe refactoring, while allowing local escape hatches when necessary

Source of truth by folder

  • eslint/: preset and rule composition source files
  • oxlint/: best-effort Oxlint presets/rules/styles (see oxlint/GAPS.md and oxlint/improve-parity.prompt.md)
  • prettier/: exported Prettier config
  • oxfmt/: exported Oxfmt config (best-effort Prettier parity; pick one formatter — see oxfmt/GAPS.md)
  • typescript/: exported tsconfig JSON presets and helper glue
  • semantic-release/: release preset exports
  • ai/: agent styleguide/rules and migration guidance
  • .vscode/: reference workspace/editor settings
  • tools/: release/build helper scripts

Do not edit dist/ manually (it is build output).

How to work in this repo

Package and runtime assumptions

  • Package manager: npm
  • Module format: ESM ("type": "module")
  • Main artifact model: source configs are authored in repo folders and exported via package.json exports

Coding and change principles

  • Keep changes minimal, localized, and backwards compatible unless breaking behavior is explicitly requested.
  • Preserve published export paths and config names unless migration is clearly part of the task.
  • Prefer extending recommended rule sets over bespoke one-off logic when possible.
  • Align changes with repo philosophy: objective linting/type-safety improvements over subjective style churn.
  • Keep examples/tests realistic and focused on expected diagnostics.

Read the full file on GitHub · 164 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 · 164 lines · 1,885 tokens per session scan A 95ded34a6de8

Subscribe to this mod's changes

configs AGENTS.md is an instructions file published in the GitHub repository peerigon/configs (4 stars, last pushed today), licensed MIT. It adds 1,885 tokens to every session, about $0.0075 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

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,261 tokens