agentmods.dev

session-graph AGENTS.md

Project instructions for a software repository that define how code changes move from feature branches into development, validation, main, and production. They also set rules for testing, deployment, and keeping commits focused.

In plain words
What is it for?
Use them when changing the repository to choose the right branch, validate changes, promote releases, rebuild production, preserve service data, and record the deployed code version.
Why use it?
They reduce the risk of deploying untested code or losing important production data during releases.

Instructions file for CodexOpenCode

109 1mo ago A scan 237 tokens original Apache-2.0
View the source file robertoshimizu/session-graph
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/robertoshimizu/session-graph/agents-md
Clone the repo
git clone --depth 1 https://github.com/robertoshimizu/session-graph

Made for: Codex, OpenCode.

Per session 237 This file is loaded in full into every session.
When invoked 237 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.00237 $0.00237
Opus 5 $0.00118 $0.00118
Sonnet 5 $0.00047 $0.00047
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

session-graph 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 · 25 lines

What it actually says

AGENTS.md — Project Rules

Branch and Production Workflow

Use this promotion path for every change:

feature/* → development → validation → main → production rebuild
  • Create feature branches from development; merge completed features back into development.
  • Validate development with compilation, parser/integration checks, and relevant live-service verification before promotion.
  • main must match the exact production version. Never merge unvalidated work directly into main.
  • After promoting development to main, push both branches and rebuild/restart production from a clean main checkout.
  • Preserve Fuseki and RabbitMQ Docker volumes during deployment.
  • Record or verify the deployed Git SHA; do not claim production alignment without evidence.
  • Begin new feature work only when development and main accurately represent their environments.

Change Discipline

  • Keep feature commits focused; do not mix provider refactors with ingestion or release changes.
  • Do not modify human-authored tests to make a change pass.
  • Do not commit generated outputs, caches, credentials, or runtime logs.
  • Update CHANGELOG.md for completed user-visible or architectural work.
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 · 25 lines · 237 tokens per session scan A c19a8f37280b

Subscribe to this mod's changes

session-graph AGENTS.md is an instructions file published in the GitHub repository robertoshimizu/session-graph (109 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 237 tokens to every session, about $0.0012 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.

DevOps and cloudGit and workflowTestingai-sessionsapache-jenaclaude-codedeveloper-toolsknowledge-graphontology
Related

Other instructions, from other repositories

ontology-atlas AGENTS.md

Instructions for wlsdks/ontology-atlas, covering agents.md — ontology-atlas, product and non-negotiable architecture, start here, structure and routes and operating gates and skills.

wlsdks/ontology-atlas · 2,685 tokens

ontology-atlas CLAUDE.md

Instructions for wlsdks/ontology-atlas, covering claude.md, visibility and mirrors, claude code loading and synchronization.

wlsdks/ontology-atlas · 579 tokens

open-kgo AGENTS.md

Instructions for mloda-ai/open-kgo, covering agents.md, environment, dependencies, running checks and run individual checks.

mloda-ai/open-kgo · 1,264 tokens

AnythingGraph AGENTS.md

Instructions for AnythingGraph/AnythingGraph, covering agents.md — anything cli mcp authoring guide, golden rules, exploring a source (no playbook), admin workflow and playbook json (compact).

AnythingGraph/AnythingGraph · 1,452 tokens

DocTology AGENTS.md

AGENTS.md instructions for tteggu87/DocTology, covering doctology agent contract, working rules, reading order, definition of done and codegraph.

tteggu87/DocTology · 379 tokens

heritagegraph AGENTS.md

AGENTS.md instructions for CAIRNepal/heritagegraph, covering agents.md — ai agent instructions for heritagegraph, 🧠 what is this project?, 📁 repository structure, ⚠️ critical rules — read before coding and 1. never hardcode secrets.

CAIRNepal/heritagegraph · 2,830 tokens