APEX AGENTS.md

A set of project instructions for AI coding agents, including project details, coding conventions, architecture rules, and workflow requirements. It treats the AGENTS.md file as the project’s shared memory.

In plain words
What is it for?
It guides branching, validation, pull-request preparation, commit messages, task boundaries, secret handling, and failing-test responses.
Why use it?
It keeps changes aligned with the repository’s standards and reduces risks such as unreviewed work, leaked credentials, or broken tests being ignored.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/othmanadi/apex/agents-md
Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/APEX

Made for: Codex, OpenCode.

Per session 217 This file is loaded in full into every session.
When invoked 217 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00217 $0.00217
Opus 5 $0.00109 $0.00109
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00022 $0.00022

Measured 2d ago against content hash 1bff0e7ca8bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

APEX 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 2d 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 · 38 lines

What it actually says

AGENTS.md — Project Intelligence

This file is the project's living memory. It is read by AI agents before every task. Rules are added automatically via apex-learn when patterns are discovered. Do not delete rules without understanding why they were added.

Identity

  • Project: {PROJECT_NAME}
  • Stack: {TECH_STACK}
  • Package Manager: {PACKAGE_MANAGER}

Code Style

Architecture Rules

Workflow

  • Always create a feature branch before making changes
  • Run the full validation chain (lint, types, tests, build) before committing
  • Open draft PRs for review — never push directly to main
  • Write descriptive commit messages: type(scope): description

Boundaries

  • Never modify files outside the assigned task scope
  • Never commit secrets, API keys, or credentials
  • Never remove failing tests — fix them or flag for review
  • Never push to main or production branches directly

Preferences

Tools

Learnings Log

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. 2d ago First seen · 38 lines · 217 tokens per session scan A 1bff0e7ca8bb

Subscribe to this mod's changes

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

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

spec-kit AGENTS.md

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.

github/spec-kit · 7,104 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,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens