agentic-engineering AGENTS.md

Repository instructions for an agent-focused project containing code, documentation, skills, integrations, and a knowledge-base server. They describe the project layout, tests, and rules for evidence and tool neutrality.

In plain words
What is it for?
Use them when changing the knowledge-base server, skills, guides, integrations, templates, or examples, and when running the project tests.
Why use it?
They give coding agents consistent project boundaries and checks, reducing unclear structure, unsupported claims, and vendor-specific assumptions.

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/wrannaman/agentic-engineering/agents-md
Clone the repo
git clone --depth 1 https://github.com/wrannaman/agentic-engineering

Made for: Codex, OpenCode.

Per session 224 This file is loaded in full into every session.
When invoked 224 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.00224 $0.00224
Opus 5 $0.00112 $0.00112
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

agentic-engineering 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 · 27 lines

What it actually says

AGENTS.md

This repo is an agentic engineering architecture. Part docs, part code, part skills.

Build & Test (KB Server)

cd apps/kb-server
python -m venv .venv && source .venv/bin/activate
pip install -e .
pytest tests/

Repo Structure

  • apps/kb-server/ — Python MCP knowledge base server
  • skills/ — 18 agent skills + 5 hooks (markdown)
  • guides/ — documentation (markdown)
  • integrations/ — review bot, OTEL configs
  • templates/ — starter configs for client repos
  • examples/ — seed KB docs and sample project

Rules

  • No vendor or company-specific branding — this repo is open source and tool-agnostic
  • Skills should work with any coding agent, not just Claude Code
  • Keep guides concise — Hemingway, not Tolstoy
  • KB server must stay under 1000 lines of Python
  • Every claim needs evidence (link to source)
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 · 27 lines · 224 tokens per session scan A 4adf15ba8b5e

Subscribe to this mod's changes

agentic-engineering AGENTS.md is an instructions file published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 224 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