graph-tool-call AGENTS.md

Repository instructions for SonAIengine/graph-tool-call. They tell the coding agent to read `docs/agent-guide.md` first and keep agent-specific notes minimal.

In plain words
What is it for?
Use them when working on that repository so the agent follows its documented contribution and workflow rules.
Why use it?
They provide a shared starting point for project rules, development commands, and testing expectations.

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

Made for: Codex, OpenCode.

Per session 95 This file is loaded in full into every session.
When invoked 95 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.00095 $0.00095
Opus 5 $0.00048 $0.00048
Sonnet 5 $0.00019 $0.00019
Haiku 4.5 $0.00010 $0.00010

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

Security

Grade A, and why

graph-tool-call 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 · 9 lines

What it actually says

Codex Entry

이 저장소의 공통 에이전트 규칙은 docs/agent-guide.md에 있다. Codex는 먼저 이 문서를 기준으로 작업한다.

Codex 메모

  • 프로젝트 공통 규칙, 개발 명령, 테스트 기준은 공통 문서를 따른다.
  • Codex 전용 규칙이 추가로 생길 때만 이 파일에 최소한으로 적는다.
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 · 9 lines · 95 tokens per session scan A c76c275023c9

Subscribe to this mod's changes

graph-tool-call AGENTS.md is an instructions file published in the GitHub repository SonAIengine/graph-tool-call (16 stars, last pushed 10d ago), licensed MIT. It adds 95 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.