A command that creates SQL queries to validate changed data models and can run those queries against a development database. SQL is a language for asking questions of a database.

Use it to generate validation files, build and run the checks, or run already-generated checks without rebuilding.

It helps check whether a code change leaves the database in the expected state, while separating query creation from execution.

mc-validate — Command for Claude Code and Cursor by monte-carlo-data

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/monte-carlo-data/mc-agent-toolkit

Made for: Claude Code, Cursor.

Or install mc-agent-toolkit, the plugin that ships this one along with the rest of its 1 command.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/monte-carlo-data/mc-agent-toolkit/mc-validate/github.svg)](https://agentmods.dev/commands/monte-carlo-data/mc-agent-toolkit/mc-validate)

Your own site

<a href="https://agentmods.dev/commands/monte-carlo-data/mc-agent-toolkit/mc-validate"><img src="https://agentmods.dev/badge/commands/monte-carlo-data/mc-agent-toolkit/mc-validate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/monte-carlo-data/mc-agent-toolkit/mc-validate"><img src="https://agentmods.dev/badge/commands/monte-carlo-data/mc-agent-toolkit/mc-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 586 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00586
Opus 5.5	$0.00004	$0.00234
Sonnet 5.5	$0.00002	$0.00117
Haiku 4.5	$0.00001	$0.00059

Measured 1mo ago against content hash 262cdeae7eac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mc-validate 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 1mo 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.

plugins/cursor/commands/mc-validate.md · 35 lines

What it actually says

Parse $ARGUMENTS to decide which mode to run. The Monte Carlo Prevent skill defines four supported invocations:

Invocation	Mode	Workflows
(empty)	default generate	W3 only
`generate`	explicit generate	W3 only
`run`	full validate	W4.1 (Build) → W4.2 (Execute)
`run --skip-build`	execute-only	W4.2 only

run also accepts --dev-db <NAME> to bypass the dev-database prompt in W4.2. Flags can combine: run --skip-build --dev-db <NAME>.

run does not auto-generate. If no validation/<table>_<ts>.sql exists for the current session's changed models, abort and tell the engineer:

"No validation queries found for <table_name>. Run /mc-validate (or /mc-validate generate) first to generate them, then re-run /mc-validate run."

Decision rules:

If $ARGUMENTS is empty or starts with generate: generate-only mode. Run Workflow 3 from the Monte Carlo Prevent skill. Save queries to validation/<table_name>_<timestamp>.sql. At the end, always offer the four next-step options described in W3 step 6 of references/workflows.md (say continue to auto-run /mc-validate run, run it yourself, run with --skip-build, or substitute <YOUR_DEV_DATABASE> and run manually).
If $ARGUMENTS starts with run: run mode.
1. Verify a validation/<table>_<ts>.sql exists for the current session's changed models. If none exist, abort with the message above. Do not run W3.
2. If --skip-build is not present: run Workflow 4.1 (Build), then Workflow 4.2 (Execute).
3. If --skip-build is present: skip W4.1 and run Workflow 4.2 directly. Assume the engineer built manually.
4. If --dev-db <NAME> is present: pass <NAME> into W4.2 and skip its dev-database confirmation prompt.
Any other token after run that isn't --skip-build or --dev-db <NAME> is an error — surface it to the engineer and stop.

Workflow definitions live in the Monte Carlo Prevent skill's references/workflows.md. Read that file before executing either mode.

Arguments: $ARGUMENTS

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.

1mo ago First seen · 35 lines · 9 tokens per session scan A 262cdeae7eac

Subscribe to this mod's changes

mc-validate is a command published in the GitHub repository monte-carlo-data/mc-agent-toolkit (93 stars, last pushed yesterday), licensed Apache-2.0. It adds 9 tokens to every session and 586 once invoked, about $0.0000 per session on Opus 5.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.

Claude Code Databases agent-observability agent-skills ai-agents cursor data-observability

pull

Refreshes local project state from a linked Supabase project or branch in one step, instead of running config pull, db pull, migration fetch, and functions download individually. It runs four steps, always in this order: pull config into supabase/config.toml, optionally fetch the remote migration history table into…

fcakyon/claude-codex-settings · 0 tokens

init

Initialize configurations for Supabase local development.

fcakyon/claude-codex-settings · 0 tokens

db-context-postgres

Validate that a non-Supabase Postgres database (Cloud SQL, RDS, self-hosted) is reachable, introspect a scoped subset of its schema, and persist it as DBCONTEXT.md. Read-only, opt-in. Use when work touches that database and planning needs verified schema, or DBCONTEXT.md is stale. Do not use without a task (run…

Mozurok/fhorja.dev · 113 tokens

cleanup

Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.

Chappygo-OS/Atomic-Spec · 17 tokens

setup-bigquery.es

Command "setup-bigquery.es" from minicoohei/ai-agent-camp, covering configuración de autenticación bigquery / gcp, step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: instalación de gcloud cli.

minicoohei/ai-agent-camp · 2 tokens

start-12-4

A guided lesson for creating files and workspace pages, either as simple pages or with body text supplied through a command pipeline.