agentmods.dev

graph-engineering-architectures AGENTS.md

graph-engineering-architectures AGENTS.md is an instructions file for Codex, OpenCode from Mark393295827/graph-engineering-architectures. It costs 459 tokens per session, scanned A, original, MIT.

Repository instructions for designing software as bounded directed graphs: workflows where nodes connect through one-way edges and explicit joins. They define rules for state, recovery, scheduling, permissions, context limits, and evidence before claiming completion.

In plain words
What is it for?
Use them when changing graph architecture, relationships, or supporting files, including updating the architecture manifest, preserving copied-file provenance, and adding finite, verifiable behavior.
Why use it?
They prevent graph workflows from becoming unpredictable through cycles, hidden joins, competing writers, unlimited retries, or replaying the whole graph after a local failure.

Instructions file for CodexOpenCode

not rated 2 13d ago A scan 459 tokens original MIT
View the source file Mark393295827/graph-engineering-architectures
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/mark393295827/graph-engineering-architectures/agents-md
Clone the repo
git clone --depth 1 https://github.com/Mark393295827/graph-engineering-architectures

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 graph-engineering-architectures AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mark393295827/graph-engineering-architectures/agents-md.svg)](https://agentmods.dev/instructions/mark393295827/graph-engineering-architectures/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/mark393295827/graph-engineering-architectures/agents-md"><img src="https://agentmods.dev/badge/instructions/mark393295827/graph-engineering-architectures/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 459 This file is loaded in full into every session.
When invoked 459 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.00459 $0.00459
Opus 5 $0.00230 $0.00230
Sonnet 5 $0.00092 $0.00092
Haiku 4.5 $0.00046 $0.00046

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

Security

Grade A, and why

graph-engineering-architectures 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.

AGENTS.md · 51 lines

How it starts

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

Graph Engineering Architectures - Agent Instructions

This repository is a focused extraction of the Graph Engineering architecture and its adjacent execution contracts.

Scope

  • Graph Engineering owns bounded static DAG topology, typed edges, explicit joins, single writers, deterministic readiness, durable graph state, and node-local recovery.
  • Loop Engineering owns temporal repetition.
  • Agent Teams Command owns process ownership, IPC, isolated work, integration, and cleanup.
  • Harness Engineering owns scheduling, permissions, leases, tools, observability, and production recovery.
  • Context Manager owns context budgets, checkpoints, and payload transfer.
  • Verify Before Claim owns evidence gates and completion claims.
  • OODA Core is a node-local adaptation example, not graph topology.

Do not add dynamic graph expansion, graph cycles, hidden joins, overlapping writers, unbounded retries, or whole-graph replay as a convenience.

Change Contract

  1. Update architecture-manifest.json when an architecture, relationship, or supporting asset changes.
  2. Preserve upstream provenance for copied files.
  3. Give every new graph behavior a finite budget, objective verifier, failure status, recovery path, and durable receipt.
  4. Keep Graph, Loop, Teams, and Harness responsibilities MECE.
  5. Add or update tests before claiming an invariant.

Required Checks

python -m unittest discover -s tools -p "test_*.py" -v
python -m unittest discover -s experiments/graph-engineering/tests -p "test_*.py" -v
python skills/graph-engineering/scripts/validate_graph_contract.py `
  skills/graph-engineering/references/diamond-graph-example.json --strict
python skills/graph-engineering/scripts/validate_graph_contract.py `
  blueprint/default-blueprint.json --strict
python tools/graph_admission_gate.py blueprint/default-blueprint.json --strict
python tools/validate_dynamic_contracts.py --strict
python skills/loop-engineering/scripts/validate_loop_contract.py `
  skills/loop-engineering/references/ci-repair-loop-example.md --strict
node --test blueprint/model.test.js
node core/ooda/ooda_loop.test.js

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

  1. 3d ago First seen · 51 lines · 459 tokens per session scan A e83f44ac50c0

Subscribe to this mod's changes

graph-engineering-architectures AGENTS.md is an instructions file published in the GitHub repository Mark393295827/graph-engineering-architectures (2 stars, last pushed 13d ago), licensed MIT. It adds 459 tokens to every session, about $0.0023 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.

Multi-AgentOrchestrationPlanningagent-skillsagentic-aidaggraph-engineering
Related

Other instructions, from other repositories

graph-engineering-workflow AGENTS.md

Instructions for Thanarak-q/graph-engineering-workflow, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.

Thanarak-q/graph-engineering-workflow · 924 tokens

paperclip-plugin-company-wizard CLAUDE.md

Instructions for Yesterday-AI/paperclip-plugin-company-wizard, covering claude.md, what this is, commands, architecture and source layout.

Yesterday-AI/paperclip-plugin-company-wizard · 2,705 tokens

paperclip-plugin-company-wizard AGENTS.md

Instructions for Yesterday-AI/paperclip-plugin-company-wizard, covering company wizard — project vision, what, why, core idea: gracefully optimistic architecture and design principles.

Yesterday-AI/paperclip-plugin-company-wizard · 1,078 tokens

team-shinchan AGENTS.md

Instructions for seokan-jeong/team-shinchan, covering agents.md - team-shinchan agent map, layer architecture, agent registry, call flow and quick reference.

seokan-jeong/team-shinchan · 910 tokens

GraphEngineering AGENTS.md

Instructions for reacher-z/GraphEngineering, covering repository agent guidance, product invariants, ownership during parallel work and verification.

reacher-z/GraphEngineering · 284 tokens

team-shinchan CLAUDE.md

Instructions for seokan-jeong/team-shinchan, covering team-shinchan plugin, repository-specific notes and source layer (src/).

seokan-jeong/team-shinchan · 450 tokens