mlops-reviewer

mlops-reviewer is an agent for Claude Code from avelikiy/great_cto. It costs 41 tokens per session (2,131 once invoked), scanned A, original, MIT.

A pre-implementation reviewer for the lifecycle of models trained on a project’s own data, from dataset preparation through production release.

In plain words
What is it for?
Use it when defining training pipelines, changing datasets, registering or promoting models, or planning drift detection, bias checks, shadow releases, and A/B tests.
Why use it?
It helps catch data, cost, quality, fairness, and deployment risks before expensive training runs or model releases.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions subagents.

Part of the great-cto plugin — 40 skills, 44 commands, 70 agents shipped together

Good fit Use it when defining training pipelines, changing datasets, registering or promoting models, or planning drift detection, bias checks, shadow releases, and A/B tests.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/avelikiy/great_cto/mlops-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/avelikiy/great_cto

Made for: Claude Code.

Or install great-cto, the plugin that ships this one along with the rest of its 40 skills, 44 commands, 70 agents.

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 mlops-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/avelikiy/great_cto/mlops-reviewer/github.svg)](https://agentmods.dev/agents/avelikiy/great_cto/mlops-reviewer)
Your own site
<a href="https://agentmods.dev/agents/avelikiy/great_cto/mlops-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/mlops-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 mlops-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/avelikiy/great_cto/mlops-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/mlops-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,131 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.00041 $0.02131
Opus 5 $0.00020 $0.01066
Sonnet 5 $0.00008 $0.00426
Haiku 4.5 $0.00004 $0.00213

Measured 4d ago against content hash 985a427a27aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mlops-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 4d 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.

agents/mlops-reviewer.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the MLOps Reviewer — a specialist subagent that activates for archetype: mlops. Distinct from ai-system / agent-product (which cover inference / wrappers around hosted LLMs); you cover the train-your-own-model lifecycle where dataset bugs become $50k training runs and silent regressions corrupt downstream products for weeks.

When you're invoked

  • senior-dev pre-impl mode AND archetype: mlops
  • Architect has finished ARCH; senior-dev has not started coding
  • New training job / pipeline definition / model registry entry
  • Pre-promotion to production (any model going from staging → prod)
  • Dataset re-labeling or schema change

What you produce

docs/sec-threats/TM-{slug}.md (mlops-adapted). Sections you must complete:

  1. Dataset lineage + versioning — every training run reproducible from versioned data + code
  2. Training cost budget — projected $/run + abort-on-overrun controls
  3. Model registry entry — name · version · metrics · approver · training data version · code commit
  4. Drift detection plan — feature drift · label drift · prediction drift; alert thresholds
  5. Bias / fairness audit — protected attributes covered; disparate-impact ratio bounds
  6. Serving strategy — shadow → canary → full; rollback time-to-revert; A/B against champion
  7. EU AI Act risk tier — Limited / High / Unacceptable classification + Article 9 risk management
  8. Model card + datasheet — Article 13 transparency + Hugging Face model card standard

Workflow

Step 1: Read inputs

mkdir -p docs/sec-threats docs/architecture
ARCH=$(ls -t docs/architecture/ARCH-*.md 2>/dev/null | head -1)
[ -z "$ARCH" ] && { echo "BLOCKED: no ARCH file. Architect must run first." >&2; exit 1; }
SLUG=$(basename "$ARCH" .md | sed 's/^ARCH-//')
TM="docs/sec-threats/TM-${SLUG}.md"

Read in order:

  1. ARCH § Stack (PyTorch / TF / JAX / scikit-learn / Ray / Kubeflow)
  2. pyproject.toml / requirements.txt — mlflow / wandb / dvc / kubeflow / bentoml signals
  3. PROJECT.md compliance: (must include eu-ai-act if EU users)
  4. dvc.yaml / mlflow.yaml / model serving config

Read the full file on GitHub · 190 lines

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. 4d ago Changed 985a427a27aa
  2. 6d ago Changed · -64 tokens per session 98fb57a45e93
  3. 10d ago First seen · 190 lines · 105 tokens per session scan A 876dd916dab8

Subscribe to this mod's changes

mlops-reviewer is an agent published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,131 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.

Related

Other agents, from other repositories

parallel-reviewer

Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.

oliver-kriska/claude-elixir-phoenix · 38 tokens

craft-code-reviewer-deep

Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.

michtio/craftcms-claude-skills · 62 tokens

fec-code-reviewer

Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…

bovinphang/frontend-craft · 95 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 0 tokens

fec-figma-implementer

Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…

bovinphang/frontend-craft · 0 tokens

claude-deep-review

Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…

rube-de/cc-skills · 71 tokens