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.
npx agentmods add agents/ranteck/graph-engineer/doc-consistency-reviewergit clone --depth 1 https://github.com/Ranteck/graph-engineerWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00080 | $0.00818 |
| Opus 5 | $0.00040 | $0.00409 |
| Sonnet 5 | $0.00016 | $0.00164 |
| Haiku 4.5 | $0.00008 | $0.00082 |
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 3d 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.
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.mdREADME.mdskills/graph-engineer/references/*.mdAGENTS.md,PROJECT_CONTEXT.mdwhen relevant to a claim
Check specifically:
- 8-node cycle: PRE-FLIGHT → SPEC → IMPL → QUALITY GATE → CRITIQUE → DEBATE/TRIAGE → REFACTOR → VERIFY, same order and names, in both
SKILL.mdandREADME.md. Elevated assurance must read as a variant of node 4, never a 9th node. - Single entry point: every Codex interaction routes through
codex:codex-rescue— flag any other/codex:*command invoked programmatically by the skill. - Pinned plugin version:
openai-codexv1.0.6 must be the same version string inREADME.md,SKILL.md, andsources.md. If one was bumped, the other two need review — don't assume a bump elsewhere is safe without re-checkingsources.md's Verification method section (the elevated-assurance fan-in barrier depends on--resume-lastsemantics from that pin). - Claude never edits implementation files: scan for any new wording in
SKILL.mdthat would have Claude use Edit/Write on implementation content, outside the one narrow exception (checkpointgit commitafter a passing QUALITY GATE, never touching tracked file content). --write/--resume-lastrules: defaultcodexpath 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.- 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.
- Anti-loop cutoff: escalates to the user, does not itself end a
/goal-bound turn unless the user's/goaltext has an explicit stop/escalate clause. - Elevated write-authorized
/goaltemplate: lives only ingoal-templates.mdbetween<!-- elevated-write-goal:start/end -->markers — flag ifREADME.mdhas re-duplicated it. - Terminology: "graph engineering" framed as this skill's own term, not an official Anthropic/OpenAI feature; not confused with the unrelated
launchdarkly/agent-graphsproject.
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.
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.
- 3d ago First seen · 27 lines · 80 tokens per session scan A 12aed3542052
doc-consistency-reviewer is an agent published in the GitHub repository Ranteck/graph-engineer (101 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 818 once invoked, about $0.0004 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.