What is ai-agent-automation AGENTS.md?

A repository instruction file for a monorepo, which is one repository containing several related applications or packages. It documents a backend, frontend, Docker-based infrastructure, development commands, tests, formatting, and commit checks.

Setting up the Node.js backend and Next.js frontend, running the worker and Docker services, executing backend tests, linting, formatting, and understanding Git hooks.

It gives agents the project structure and exact commands needed to run, test, format, and safely commit changes across the separate parts.

How vmDeshpande/ai-agent-automation configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to vmDeshpande/ai-agent-automation. 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/vmDeshpande/ai-agent-automation/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/vmDeshpande/ai-agent-automation

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/vmdeshpande/ai-agent-automation/agents-md/github.svg)](https://agentmods.dev/instructions/vmdeshpande/ai-agent-automation/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/vmdeshpande/ai-agent-automation/agents-md"><img src="https://agentmods.dev/badge/instructions/vmdeshpande/ai-agent-automation/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/vmdeshpande/ai-agent-automation/agents-md"><img src="https://agentmods.dev/badge/instructions/vmdeshpande/ai-agent-automation/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,887 This file is loaded in full into every session.

When invoked 3,887 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.

Model	Per session	Once invoked
Fable 5.1	$0.03887	$0.03887
Opus 5	$0.01944	$0.01944
Sonnet 5	$0.00777	$0.00777
Haiku 4.5	$0.00389	$0.00389

Measured 9d ago against content hash 1263a7a90ce1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ai-agent-automation 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 9d 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 · 116 lines

How it starts

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

AGENTS.md

Repo Structure

Monorepo with three packages that are NOT linked via workspaces — each has its own node_modules:

backend/ — Node.js/Express, CommonJS ("type": "commonjs"), entry point server.js
frontend/ — Next.js 16 + React 19 + TypeScript, entry point src/app/
infra/ — Docker Compose stack (MongoDB, backend, worker, frontend, nginx)

Dev Commands

Backend (two processes required):

cd backend
cp .env.example .env   # fill in JWT_SECRET, MONGO_URI, LLM keys
npm install
npm run dev             # API server on :5000
npm run worker          # agent runner (separate terminal)

Frontend:

cd frontend
npm install
npm run dev             # Next.js on :3000

Lint & format (run from repo root):

npm run lint            # eslint frontend/src + backend/src
npm run format          # prettier --write frontend/src backend/src

Backend tests:

cd backend
npm test                # runs jest --testMatch '**/*.handler.test.js'

Only handler test files are included. There is no frontend test suite.

Git Hooks

Husky runs on commit:

pre-commit: lint-staged → eslint --fix + prettier --write on staged files
commit-msg: commitlint enforces Conventional Commits

Allowed types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert. Header max 100 chars, subject lowercase, no trailing period.

Code Style

Backend JS: prefer-const, eqeqeq, no var, no throw literal, no return await
Frontend TS: @typescript-eslint/consistent-type-imports enforced, no-explicit-any as warning, React hooks rules enforced
Prettier: semi, singleQuote, tabWidth 2, trailingComma es5, printWidth 100, bracketSpacing, arrowParens always

Architecture Notes

Backend and frontend are separate processes communicating over REST + MongoDB
MongoDB must run with replica set enabled (Docker compose handles this via mongo-init-replica)
Worker (npm run worker / node src/agents/runner.js) polls for tasks — must run alongside the API server
backend/src/ layout: agents/, config/, controllers/, models/, routes/, services/, tools/, workflow/
Frontend API URL in Docker is derived from BACKEND_PORT — do NOT set NEXT_PUBLIC_API_URL manually for Docker deploys
Env vars are never committed; backend/.env.example is the source of truth for local dev, infra/.env.example for Docker

Read the full file on GitHub · 116 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.

9d ago First seen · 116 lines · 3,887 tokens per session scan A 1263a7a90ce1

Subscribe to this mod's changes

ai-agent-automation AGENTS.md is an instructions file published in the GitHub repository vmDeshpande/ai-agent-automation (178 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,887 tokens to every session, about $0.0194 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-30.

LLM Workflow Automation ai ai-agents nodejs open-source

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

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.

openai/codex · 5,153 tokens

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 · 6,785 tokens

ai-agent-automation: Instructions file for Codex