knowledge-graph AGENTS.md

Project instructions for the Knowledge Graph memory layer, including its source files, validation commands, runtime data rules, and guidance for storing durable knowledge.

In plain words
What is it for?
Use them before changing the project, especially when editing the installer, shell scripts, memory skills, or MCP server. They also describe how to inspect the knowledge graph first.
Why use it?
They tell the coding agent how to work safely in this repository and which files are authoritative when instructions overlap.

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/hilyfux/knowledge-graph/agents-md
Clone the repo
git clone --depth 1 https://github.com/hilyfux/knowledge-graph

Made for: Codex, OpenCode.

Per session 371 This file is loaded in full into every session.
When invoked 371 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.00371 $0.00371
Opus 5 $0.00186 $0.00186
Sonnet 5 $0.00074 $0.00074
Haiku 4.5 $0.00037 $0.00037

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

Security

Grade A, and why

knowledge-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 · 23 lines

What it actually says

Project Instructions

This repository builds Knowledge Graph, a bash + jq memory layer for AI coding agents. Treat standalone/ as the packaged installer/runtime surface and keep skills/knowledge-graph/ in sync when changing shared skill or script behavior.

Knowledge Graph

  • Source of truth for runtime behavior: standalone/skills/knowledge-graph/scripts/.
  • Main validation command: bash tests/test-pipeline.sh.
  • Installer validation: bash -n standalone/install.sh standalone/skills/knowledge-graph/scripts/*.sh and, when available, shellcheck standalone/install.sh standalone/skills/knowledge-graph/scripts/*.sh.
  • Durable knowledge nodes are canonical CLAUDE.md and SKILL.md files. AGENTS.md is only a Codex adapter and must not duplicate module knowledge.
  • Codex/MCP runtime should prefer KG_PROJECT_DIR for non-Claude scripts. Claude Code may still set CLAUDE_PROJECT_DIR.
  • Do not commit .knowledge-graph/ runtime data.

Knowledge Graph

  • Use the bundled MCP server in .mcp.json when available: start with kg_status, then kg_query or kg_read_node before editing unfamiliar modules.
  • Durable module knowledge lives in canonical CLAUDE.md and SKILL.md files. AGENTS.md is only the Codex adapter that tells Codex to read those canonical nodes through MCP.
  • Runtime data lives under .knowledge-graph/ and should stay uncommitted.
  • If running scripts outside Claude Code, set KG_PROJECT_DIR to this project root; Claude Code may set CLAUDE_PROJECT_DIR instead.
  • Before reporting success, include concrete evidence: tests run, files checked, or MCP resources consulted.
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 · 23 lines · 371 tokens per session scan A f3a656b3a0fc

Subscribe to this mod's changes

knowledge-graph AGENTS.md is an instructions file published in the GitHub repository hilyfux/knowledge-graph (17 stars, last pushed 2mo ago), licensed MIT. It adds 371 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-30.

Related

Other instructions, from other repositories

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

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

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