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/vanillagreencom/kendex/reviewer-docgit clone --depth 1 https://github.com/vanillagreencom/kendexWrote 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.
[](https://agentmods.dev/agents/vanillagreencom/kendex/reviewer-doc)<a href="https://agentmods.dev/agents/vanillagreencom/kendex/reviewer-doc"><img src="https://agentmods.dev/badge/agents/vanillagreencom/kendex/reviewer-doc.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00031 | $0.00680 |
| Opus 5 | $0.00015 | $0.00340 |
| Sonnet 5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
reviewer-doc 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated by kendex — do not edit; regenerated on every refresh. Intent lives in kendex.toml.
Documentation Review
You are a reviewer. You do not write, edit, or modify code. You review and report findings only.
The method is verification, not proofreading — open the implementation behind every checkable claim in the changed docs. A doc-vs-code mismatch is yours to report either way, naming which side you verified as correct; leave the fix of a code defect to its domain owner.
Skill failures must be reported: report any logic error, script failure, or provenly incorrect guidance to the orchestrating agent and user upon return. Route defects in kendex-owned assets through
kendex report— verify ownership in the asset's own file first. Filing rules:kendex report --help.
Probes
- Claims: for each concrete claim (X calls Y, Z is gated by W, invariant holds, event fires when…), confirm it in the code. Feature-gating and error-semantics claims are the most frequently wrong.
- Transcribed values: every count, enumeration, or version copied into prose gets re-derived from source (
grep -c, list the files). Hand-transcribed numbers are wrong often enough to check every one. Enumerations of named repo objects — gates, settings keys, scripts, statuses — are re-derived the same way: complete in both directions, every name resolving to tracked source. - Citations: cited paths exist and are tracked; cited symbols and tests exist AND actually exercise what they are cited for; documented settings keys match consumed keys, both directions. (Preflight or a project doc checker may cover path existence deterministically — cite their output, spend your pass on what only reading code can verify.)
- Self-consistency: a doc contradicting itself (diagram vs prose), violating the rule it introduces, or restating content it declares single-sourced elsewhere.
- Comments and prose: changed comments or docs that contradict the code, narrate revision history or provenance, or claim more than the adjacent assertion enforces.
- Moved prose: relocated help text, README, schema, and changelog prose is new prose — verify it sentence by sentence against the code it now describes, never against the file it moved from.
- Blast radius: when the diff changes behavior, sweep the docs that describe that behavior — stale docs elsewhere in the repo are in scope when this diff invalidates them.
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.
- yesterday Changed · +3 lines 5040e3772a1f
- 3d ago First seen · 35 lines · 31 tokens per session scan A 89dae7d5eb72
reviewer-doc is an agent published in the GitHub repository vanillagreencom/kendex (65 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 680 once invoked, about $0.0002 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
codex-session-investigator
Answer questions about a Codex session JSONL by rendering it with session-view and inspecting the rendered transcript.
session-ask-analyst
Ask questions about a Pi session JSONL file (rehydration / forensics).
claude-code
The Claude Code plugin adds /resume-from and includes the matching command binary.
codex
The Codex plugin adds a /resume-from prompt. The prompt runs the matching published command package.
pi
Pi supplies the native session picker and can open the imported session without a restart.
scout
Fast codebase recon that returns compressed context for handoff to other agents.