Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/peerigon/configs/agents-mdgit clone --depth 1 https://github.com/peerigon/configsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01885 | $0.01885 |
| Opus 5 | $0.00942 | $0.00942 |
| Sonnet 5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
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 yesterday.
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.
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
tsconfigpresets - 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 filesoxlint/: best-effort Oxlint presets/rules/styles (seeoxlint/GAPS.mdandoxlint/improve-parity.prompt.md)prettier/: exported Prettier configoxfmt/: exported Oxfmt config (best-effort Prettier parity; pick one formatter — seeoxfmt/GAPS.md)typescript/: exported tsconfig JSON presets and helper gluesemantic-release/: release preset exportsai/: agent styleguide/rules and migration guidance.vscode/: reference workspace/editor settingstools/: 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.jsonexports
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.
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.
- yesterday First seen · 164 lines · 1,885 tokens per session scan A 95ded34a6de8
configs AGENTS.md is an instructions file published in the GitHub repository peerigon/configs (4 stars, last pushed 20d ago), licensed MIT. It adds 1,885 tokens to every session, about $0.0094 per session on Opus 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.