multi-agent-system-pattern AGENTS.md

multi-agent-system-pattern AGENTS.md is an instructions file for Codex, OpenCode from vpeetla-ai/multi-agent-system-pattern. It costs 389 tokens per session, scanned A, original, MIT.

A set of project instructions for building governed multi-agent systems, where several software agents coordinate work. It describes repository conventions, architecture layers, testing expectations, and how to install the organisation's skills.

In plain words
What is it for?
Guiding development in the organisation's agent-system repositories, including planning changes, following Python and FastAPI conventions, installing skills, and verifying work with tests.
Why use it?
It gives coding agents shared rules for understanding the project and making focused changes. It also defines checks such as running the test suite before considering work complete.

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/vpeetla-ai/multi-agent-system-pattern/agents-md
Clone the repo
git clone --depth 1 https://github.com/vpeetla-ai/multi-agent-system-pattern

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 multi-agent-system-pattern AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vpeetla-ai/multi-agent-system-pattern/agents-md.svg)](https://agentmods.dev/instructions/vpeetla-ai/multi-agent-system-pattern/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/vpeetla-ai/multi-agent-system-pattern/agents-md"><img src="https://agentmods.dev/badge/instructions/vpeetla-ai/multi-agent-system-pattern/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 389 This file is loaded in full into every session.
When invoked 389 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.00389 $0.00389
Opus 5 $0.00195 $0.00195
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

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

Security

Grade A, and why

multi-agent-system-pattern 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 42 lines

What it actually says

Agent Instructions — vpeetla-ai org

Read CONTEXT.md for shared vocabulary.

Agentic engineering (Karpathy)

  1. Think before coding — state assumptions, plan, success criteria
  2. Simplicity first — minimum diff; no speculative features
  3. Surgical changes — match existing style; no drive-by refactors
  4. Goal-driven execution — tests/evals define done; iterate until pass

Stack awareness

This org builds governed agent systems, not chat demos:

  • Orchestration (VAP) and governance (AegisAI) are separate layers
  • RAG uses access-before-ranking
  • Side effects require gateway or HITL
  • Self-improvement uses harness + eval loops (LoopForge)

Repo conventions

  • Python 3.11+, FastAPI, Pydantic v2, LangGraph for agent graphs
  • pip install -e ".[dev]" + pytest -q before claiming done
  • README: badges → problem → 60s diagram → honest status table → quick start
  • Deploy: Vercel (UI) + Render (API); see render.yaml

Skills repo

Install org skills from vpeetla-ai-skills:

./scripts/install.sh --cursor --project .
./scripts/install.sh --codex --project .

When stuck

  1. Check which stack layer the task belongs to
  2. Read the target repo's docs/ECOSYSTEM.md or docs/ARCHITECTURE.md
  3. Use tdd-agent-loops for graph changes; aegis-gateway for side effects
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. 3d ago First seen · 42 lines · 389 tokens per session scan A 2ee79e251ad2

Subscribe to this mod's changes

multi-agent-system-pattern AGENTS.md is an instructions file published in the GitHub repository vpeetla-ai/multi-agent-system-pattern (2 stars, last pushed 1mo ago), licensed MIT. It adds 389 tokens to every session, about $0.0019 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