test_case_verifier

test_case_verifier is an agent for Claude Code from sfc-gh-dflippo/snowflake-dbt-demo. It costs 55 tokens per session (1,639 once invoked), scanned A, original, Apache-2.0.

An independent test reviewer for migration cases that still fail after converted code is tested. It examines the code, test results, and related evidence before accepting a failure as one that does not require a code change.

In plain words
What is it for?
It helps review remaining failed test cases for one database object and record an override acceptance only when changing the code would be illogical.
Why use it?
A failing test does not always mean the converted code is wrong; some cases may be expected or unsuitable for a code fix. This reviewer adds a separate decision instead of accepting another agent's conclusion automatically.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

Part of the snowflake-migration plugin — 72 skills, 7 agents shipped together

Good fit It helps review remaining failed test cases for one database object and record an override acceptance only when changing the code would be illogical.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier
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/sfc-gh-dflippo/snowflake-dbt-demo

Made for: Claude Code.

Or install snowflake-migration, the plugin that ships this one along with the rest of its 72 skills, 7 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 test_case_verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier/github.svg)](https://agentmods.dev/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier)
Your own site
<a href="https://agentmods.dev/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier"><img src="https://agentmods.dev/badge/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier/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 test_case_verifier

Your own site · 80×15
<a href="https://agentmods.dev/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier"><img src="https://agentmods.dev/badge/agents/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,639 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.00055 $0.01639
Opus 5 $0.00028 $0.00820
Sonnet 5 $0.00011 $0.00328
Haiku 4.5 $0.00006 $0.00164

Measured 2d ago against content hash 46bb74409f75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

test_case_verifier 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 2d 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.

.claude/skills/snowflake-migration/agents/test_case_verifier.md · 158 lines

How it starts

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

You review every remaining failing runTests case on one object, in one turn. The prompt carries objectId, projectDir, and a list of params_hash values. It may also carry a verdict, a reason, a sibling finding, or a ready-made override_accept_case call. Those are the walker's opinion. They are not evidence. Read each case and decide.

1. Attach

configure(project_dir="<projectDir>")

Pass nothing else — attach only, no dashboard or session rewrite. Cortex stamps your identity. Do not pass agent_id.

2. Read the cases

Do not decide from the prompt. For this objectId and each params_hash:

query_registry(where="id = '<objectId>'", fields="id,source,files,target")

Hold files.source.path, files.converted.path, files.artifacts.path, and source.{database,schema,name}. Then read, in this order:

  1. <metadata_database>.VALIDATION.LATEST — attach names metadata_database. Same catalog as ORCHESTRATION / RULE_ENGINE (scai test validate writes one VARIANT row per case into VALIDATION.RESULTS; LATEST is the newest run per case). It is not snowflake_database (the migration target). There is no <projectDir>/test-results/results.json.

    sql_execute one read-only SELECT. Pass connection from attach snowflake_connection:. Take status, error_message, parameters, and differences from the rows. A prompt summary that disagrees with LATEST is wrong.

    SELECT params_hash, status, parameters, error_message, differences,
           baseline_rows, actual_rows, match_type
    FROM <metadata_database>.VALIDATION.LATEST
    WHERE UPPER(procedure_name) IN (
            UPPER('<source.database>.<source.schema>.<source.name>'),
            UPPER('<source.schema>.<source.name>')
          )
      AND params_hash IN ('<hash>', …)
    
  2. The test YAML under <projectDir>/<files.artifacts.path>/test/ (glob *.yml). Find the test_cases row for each hash / params.

  3. The source SQL at files.source.path and the converted SQL at files.converted.path.

  4. Every view or column the diffs name that is not defined in the proc. query_registry for that name and read its source and converted SQL the same way.

Read the full file on GitHub · 158 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. 2d ago First seen · 158 lines · 0 tokens per session scan A 46bb74409f75

Subscribe to this mod's changes

test_case_verifier is an agent published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,639 once invoked, about $0.0003 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-09-10.

Related

Other agents, from other repositories