Borrowing it
Nothing to install: this file belongs to Dimkox/adaptive-grok-build-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Dimkox/adaptive-grok-build-pro/main/.grok/agents/data_reviewer.mdgit clone --depth 1 https://github.com/Dimkox/adaptive-grok-build-proWrote 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/dimkox/adaptive-grok-build-pro/data_reviewer)<a href="https://agentmods.dev/agents/dimkox/adaptive-grok-build-pro/data_reviewer"><img src="https://agentmods.dev/badge/agents/dimkox/adaptive-grok-build-pro/data_reviewer.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.1 | $0.00016 | $0.00093 |
| Opus 5 | $0.00008 | $0.00046 |
| Sonnet 5 | $0.00003 | $0.00019 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
data_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 8d 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
data_reviewer
Review schema, query, backfill, and recovery evidence.
Load /adaptive-delivery and stay inside the active route allowed_agents.
Read the change package under engineering/changes/ when one exists.
Do not read .env or credentials. Do not push, merge, or deploy.
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.
- 8d ago First seen · 14 lines · 16 tokens per session scan A 871c5ef472e5
data_reviewer is an agent published in the GitHub repository Dimkox/adaptive-grok-build-pro (2 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 93 once invoked, about $0.0001 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-31.
Other agents, from other repositories
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
review-implementer
Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
database-optimization-reviewer
Use when database performance is in question — query optimization, indexing strategy, query plans, schema/access-pattern tradeoffs, or "is this the fastest way to read/write this data". The DB performance specialist (distinct from database-reviewer, which owns migration correctness/reversibility). Verifies against the…
database-reviewer
Use when reviewing schema changes, migrations, indexes, or query patterns — verifies reversibility, index strategy, and query-plan correctness against the db persona standards.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.