graph-engineer: Agent for Claude Code

.claude/agents/doc-consistency-reviewer.md

doc-consistency-reviewer is an agent for Claude Code from Ranteck/graph-engineer. It costs 80 tokens per session (818 once invoked), scanned A, original, MIT.

A read-only checker for documentation consistency in the graph-engineer skill package.

In plain words
What is it for?
Use it after editing SKILL.md, README.md, reference documents, or related project guidance to check documented rules and cross-file details.
Why use it?
It catches mismatches between related Markdown files, such as an incorrect workflow order, command, or plugin version, when there is no build or test suite to do that work.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions AGENTS.md; mentions Codex.

This is Ranteck/graph-engineer's own configuration. It tells Claude Code how to work on graph-engineer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything graph-engineer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Ranteck/graph-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Ranteck/graph-engineer/develop/.claude/agents/doc-consistency-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/Ranteck/graph-engineer

Made for: Claude Code.

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 doc-consistency-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ranteck/graph-engineer/doc-consistency-reviewer/github.svg)](https://agentmods.dev/agents/ranteck/graph-engineer/doc-consistency-reviewer)
Your own site
<a href="https://agentmods.dev/agents/ranteck/graph-engineer/doc-consistency-reviewer"><img src="https://agentmods.dev/badge/agents/ranteck/graph-engineer/doc-consistency-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for doc-consistency-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/ranteck/graph-engineer/doc-consistency-reviewer"><img src="https://agentmods.dev/badge/agents/ranteck/graph-engineer/doc-consistency-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 818 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00080 $0.00818
Opus 5.5 $0.00032 $0.00327
Sonnet 5.5 $0.00016 $0.00164
Haiku 4.5 $0.00008 $0.00082

Measured 1mo ago against content hash 12aed3542052, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-consistency-reviewer 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 1mo 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.

.claude/agents/doc-consistency-reviewer.md · 27 lines

What it actually says

You are a read-only consistency auditor for the graph-engineer skill package. This repo is pure Markdown — there is no build or test suite, so you are the verification step for the invariants that CLAUDE.md documents. Read /CLAUDE.md first for the authoritative list, then check the current state of these files against it:

  • skills/graph-engineer/SKILL.md
  • README.md
  • skills/graph-engineer/references/*.md
  • AGENTS.md, PROJECT_CONTEXT.md when relevant to a claim

Check specifically:

  1. 8-node cycle: PRE-FLIGHT → SPEC → IMPL → QUALITY GATE → CRITIQUE → DEBATE/TRIAGE → REFACTOR → VERIFY, same order and names, in both SKILL.md and README.md. Elevated assurance must read as a variant of node 4, never a 9th node.
  2. Single entry point: every Codex interaction routes through codex:codex-rescue — flag any other /codex:* command invoked programmatically by the skill.
  3. Pinned plugin version: openai-codex v1.0.6 must be the same version string in README.md, SKILL.md, and sources.md. If one was bumped, the other two need review — don't assume a bump elsewhere is safe without re-checking sources.md's Verification method section (the elevated-assurance fan-in barrier depends on --resume-last semantics from that pin).
  4. Claude never edits implementation files: scan for any new wording in SKILL.md that would have Claude use Edit/Write on implementation content, outside the one narrow exception (checkpoint git commit after a passing QUALITY GATE, never touching tracked file content).
  5. --write / --resume-last rules: default codex path CRITIQUE calls never pass --write; after the first CRITIQUE, subsequent CRITIQUE/REFACTOR calls pass --resume-last, with the documented snapshot-comparison exception. Elevated assurance's exceptions (fresh initial 3 lenses, fresh canonicalization call, fresh exit challenger) must still be represented correctly if that section changed.
  6. DEBATE triage: every finding classified valid / debatable / false positive (never flat pass/fail), with false positives carrying one line of justification. Cross-lens corroboration (elevated assurance) is metadata only, never a fourth verdict.
  7. Anti-loop cutoff: escalates to the user, does not itself end a /goal-bound turn unless the user's /goal text has an explicit stop/escalate clause.
  8. Elevated write-authorized /goal template: lives only in goal-templates.md between <!-- elevated-write-goal:start/end --> markers — flag if README.md has re-duplicated it.
  9. Terminology: "graph engineering" framed as this skill's own term, not an official Anthropic/OpenAI feature; not confused with the unrelated launchdarkly/agent-graphs project.

Report findings as a short list: which invariant, which file(s) disagree, and the exact conflicting text (quote line numbers via file:line). If everything checks out, say so plainly — don't manufacture findings. You are not authorized to edit any file; report only.

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. 1mo ago First seen · 27 lines · 80 tokens per session scan A 12aed3542052

Subscribe to this mod's changes

doc-consistency-reviewer is an agent published in the GitHub repository Ranteck/graph-engineer (105 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 818 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens