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.
git clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demoWrote 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/sfc-gh-dflippo/snowflake-dbt-demo/test_case_verifier)<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.
<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>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.00055 | $0.01639 |
| Opus 5 | $0.00028 | $0.00820 |
| Sonnet 5 | $0.00011 | $0.00328 |
| Haiku 4.5 | $0.00006 | $0.00164 |
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.
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:
-
<metadata_database>.VALIDATION.LATEST— attach namesmetadata_database. Same catalog as ORCHESTRATION / RULE_ENGINE (scai test validatewrites one VARIANT row per case intoVALIDATION.RESULTS; LATEST is the newest run per case). It is notsnowflake_database(the migration target). There is no<projectDir>/test-results/results.json.sql_executeone read-onlySELECT. Passconnectionfrom attachsnowflake_connection:. Takestatus,error_message,parameters, anddifferencesfrom 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>', …) -
The test YAML under
<projectDir>/<files.artifacts.path>/test/(glob*.yml). Find thetest_casesrow for each hash / params. -
The source SQL at
files.source.pathand the converted SQL atfiles.converted.path. -
Every view or column the diffs name that is not defined in the proc.
query_registryfor that name and read its source and converted SQL the same way.
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.
- 2d ago First seen · 158 lines · 0 tokens per session scan A 46bb74409f75
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.
Other agents, from other repositories
seed-generator
Test data generator. Creates realistic seed data based on schema.
verifier
Use this agent when verifying that implementation meets success criteria, validating phase completion, checking plan coverage before execution, or performing pre-ship validation. Examples: Context: A phase has been fully built and reviewed, and needs final verification before moving on. user: "Verify that the database…
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
validation-engineer
Migration validation engineer. Designs and executes data integrity validation queries, row count matching, business rule validation, and regression test suites.
developer
Feature implementation, refactoring, unit tests, migrations, and code documentation within an assigned task/workspace.
qa-backend-mean
Backend QA engineer for MEAN stack apps. Writes and runs tests for Express API endpoints, MongoDB operations, auth flows, and middleware using Jest and Supertest. Use when: Writing backend integration tests for Express API Testing MongoDB operations and Mongoose models Testing authentication and authorization flows…