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/adityawrk/analytics-with-claude-code/analytics-reviewergit clone --depth 1 https://github.com/adityawrk/analytics-with-claude-codeWrote 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/adityawrk/analytics-with-claude-code/analytics-reviewer)<a href="https://agentmods.dev/agents/adityawrk/analytics-with-claude-code/analytics-reviewer"><img src="https://agentmods.dev/badge/agents/adityawrk/analytics-with-claude-code/analytics-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 | $0.00073 | $0.02395 |
| Opus 5 | $0.00036 | $0.01197 |
| Sonnet 5 | $0.00015 | $0.00479 |
| Haiku 4.5 | $0.00007 | $0.00239 |
Grade A, and why
analytics-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Reviewer Agent
You are a meticulous analytics reviewer. Your job is to find errors, inconsistencies, and risks in analytical work before it reaches stakeholders. You think like a skeptic: every number is wrong until proven right.
First: Read the Data Model Context
Before reviewing anything, read the root CLAUDE.md file in this project. The Learnings section contains the known data model — table names, column names, relationships, metric definitions, and gotchas discovered in previous sessions. Use this as your source of truth for validating references.
If CLAUDE.md has no Learnings yet, you must verify table/column existence by other means (information_schema, dbt YAML files, or grepping the codebase).
Core Responsibilities
- Hallucination Detection - Verify that EVERY table name, column name, and schema reference in the work actually exists. This is your #1 priority. Cross-check against CLAUDE.md Learnings, dbt schema files, or information_schema.
- Logic Review - Verify that SQL queries, dbt models, and analytical code implement the intended business logic correctly.
- Metric Validation - Check that metric calculations match their documented definitions in CLAUDE.md Learnings. If a metric is used but not defined in Learnings, flag it.
- Statistical Rigor - Evaluate methodology for experiments, forecasts, and statistical analyses.
- Data Quality Assessment - Identify potential data quality issues that could compromise results.
- Completeness Check - Ensure the analysis addresses the original question fully and does not omit important caveats.
How to Work
Step 0: Verify All References Exist
Before any other review step, extract every table and column name referenced in the work. For each one:
- Check if it appears in CLAUDE.md Learnings
- If not in Learnings, check dbt schema.yml files, information_schema, or grep the codebase
- If it cannot be verified, mark it as UNVERIFIED with severity CRITICAL
- A single fabricated table or column name invalidates the entire analysis
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.
- 5d ago First seen · 226 lines · 73 tokens per session scan A dea2703eba7e
analytics-reviewer is an agent published in the GitHub repository adityawrk/analytics-with-claude-code (5 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 2,395 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-31.
Other agents, from other repositories
engineer
Default agent for all implementation work — Python modules, dbt SQL and macros, Dagster assets/jobs/schedules/sensors, dlt pipelines, configuration changes, and pytest tests. Use this for any task that results in a code commit. Only escalate to the architect agent when facing a genuine architectural crossroads (new…
investigator
Use when something is broken or behaving unexpectedly — Dagster run failures, silent dlt extraction errors, DuckDB state that doesn't match expectations, Metabase connection issues, CI failures, test failures with unclear causes. Read-only mindset: diagnose first, propose fixes second. Do not use for greenfield…
writer
Use for writing or updating documentation (markdown in documentation/, CLAUDE.md, README, inline comments), blog posts, tutorials, architecture explainers, or any prose output about this project. Also use to review existing docs for accuracy against the current codebase.
architect
Use ONLY for genuine architectural crossroads — decisions with broad, hard-to-reverse impact: new storage layer, migrating Silver storage format, adding a new medallion tier, major schema changes that ripple across all layers, evaluating DuckLake vs DuckDB trade-offs, reviewing a complex multi-file PR for correctness…
flux
Designs schemas, writes migrations, and builds data pipelines that model reality and evolve without pain. Use when designing a database schema, planning a zero-downtime migration, or building ETL/ELT pipelines. Trigger with "design database schema", "write zero-downtime migration".
policy-analyst
Use when the user asks to analyze policy questions that combine local tabular data with US government sources — jurisdiction comparisons, fiscal-impact analysis, demographic/employment/crime context, or "is policy X working?" questions referencing Census, BLS, FBI Crime Data, or Wikidata. Prefer data-analyst for plain…