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 skills add ulises-jeremias/agent-toolkit --skill snowflake-validationgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/skills/ulises-jeremias/agent-toolkit/snowflake-validation)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/snowflake-validation"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/snowflake-validation.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.1 | $0.00036 | $0.00404 |
| Opus 5 | $0.00018 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
snowflake-validation 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 3d 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.
What it actually says
Snowflake validation (HOW)
Use when the task or repo requires Snowflake verification. Client workflows may delegate here alongside dbt-validation.
Boundaries
- Read-only validation unless the user and repo explicitly authorize DDL/DML.
- Never claim “Snowflake validation passed” or “query succeeded” without credentials and observed outputs (or explicit statement that checks were skipped).
- Do not rotate keys, change roles, or alter security objects from this skill unless the repo’s
AGENTS.mdclearly authorizes it and the user approves.
Discovery
Read repo docs for: connection method (env vars, profiles.yml, SSO), Snowflake SQL or Snowflake CLI (snow) usage, and warehouse/database/schema defaults.
Patterns
| Situation | Action |
|---|---|
| Credentials available | Run minimal SELECT statements or documented smoke queries; record that they were executed |
| Snowflake CLI documented | Use repo’s exact commands; check snow --help for current subcommands |
| No credentials | State skipped in Jira/PR; list what would be validated when access exists |
| dbt + Snowflake | Coordinate with dbt-validation; Snowflake may be exercised indirectly via dbt |
Evidence
- For each run: what ran (object or test name), environment (non-secret), result (row count, success/failure).
- Redact account identifiers if the user requests privacy in chat.
Safety
- No secrets in tickets, PRs, or command lines in logs pasted to chat—use env vars and documented patterns only.
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.
- 3d ago First seen · 39 lines · 36 tokens per session scan A 4eadae9c015d
snowflake-validation is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 404 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-09-04.
Other skills, from other repositories
iblai-api-profile-metadata
Read and write per-user, per-organization metadata via the platform API — a key-value store for user preferences, app settings, feature flags, and onboarding progress. Defaults to the signed-in user; admins can target another user. Use to persist per-user state.
review-database
Review database usage for migration safety, query performance, connection/transaction management, and schema design. Covers PostgreSQL and MySQL. Runs squawk for PostgreSQL migration linting if available. Use when the user asks for a database review, SQL review, migration review, or schema review.
backend-development
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability…
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
clickhouse-pydantic-config
Generate DBeaver config from Pydantic ClickHouse models. TRIGGERS - DBeaver config, ClickHouse connection, database client config.
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…