graphify AGENTS.md

Project-specific instructions for Graphify-Labs/graphify, a project with a generated knowledge graph stored in `graphify-out/`.

In plain words
What is it for?
Use them when answering architecture or codebase questions, navigating the project wiki, or updating the knowledge graph after modifying code.
Why use it?
They tell the agent where to find the project's architecture summary and how to keep the graph current after code changes.

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/graphify-labs/graphify/agents-md
Clone the repo
git clone --depth 1 https://github.com/Graphify-Labs/graphify

Made for: Codex, OpenCode.

Per session 90 This file is loaded in full into every session.
When invoked 90 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.00090 $0.00090
Opus 5 $0.00045 $0.00045
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

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

Security

Grade A, and why

graphify 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 yesterday.

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 · 9 lines

What it actually says

graphify

This project has a graphify knowledge graph at graphify-out/.

Rules:

  • Before answering architecture or codebase questions, read graphify-out/GRAPH_REPORT.md for god nodes and community structure
  • If graphify-out/wiki/index.md exists, navigate it instead of reading raw files
  • After modifying code files in this session, run graphify update . to keep the graph current (AST-only, no API cost)
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. yesterday First seen · 9 lines · 90 tokens per session scan A e9d98d3156b0

Subscribe to this mod's changes

graphify AGENTS.md is an instructions file published in the GitHub repository Graphify-Labs/graphify (112,912 stars, last pushed yesterday), licensed Apache-2.0. It adds 90 tokens to every session, about $0.0005 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.