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 sfc-gh-dflippo/snowflake-dbt-demo --skill resolving-ewisgit 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/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis)<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis/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/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/resolving-ewis.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.00075 | $0.00511 |
| Opus 5 | $0.00037 | $0.00255 |
| Sonnet 5 | $0.00015 | $0.00102 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
resolving-ewis 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.
What it actually says
Usage
When you encounter an EWI code (e.g., SSC-EWI-0021, SSC-EWI-TS0087):
-
Check for existing reference: Look in the
reference/folder for a file matching the EWI code (e.g.,reference/SSC-EWI-0021.md) -
If the reference exists:
- Read and follow the guidance in the reference file
- Apply the documented fix patterns to resolve the EWI
- After successfully resolving the issue, update the reference file with any new learnings, edge cases, or patterns discovered
-
If the reference does not exist:
- Resolve the EWI using your knowledge of SQL Server and Snowflake
- After successfully resolving the issue, create a new reference file (e.g.,
reference/SSC-EWI-XXXX.md) - Document the problem, fix patterns, examples, and any important considerations
Reference File Structure
Each reference file should follow this structure:
# SSC-EWI-XXXX - Brief Description
Brief explanation of what this EWI means and why it occurs.
## Quick Reference
| SQL Server | Snowflake |
|------------|-----------|
| Original syntax | Converted syntax |
## Identification
How to identify this EWI in code (markers, patterns).
## Fix Process
Step-by-step process to resolve the EWI.
## Examples
### Before
```sql
-- Invalid/unconverted code
After
-- Valid Snowflake code
Key Points
- Important considerations
- Edge cases
- Common mistakes to avoid
Resources
- Links to relevant Snowflake documentation
- Links to relevant SQL Server documentation
## Updating References
When updating an existing reference after resolving an EWI:
- Add new patterns or edge cases discovered
- Include additional examples if the fix was non-obvious
- Document any gotchas or pitfalls encountered
- Keep the file focused and well-organized
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/0073-Error-Handling.md 7.8 KB
- reference/0073-Geospatial-Methods.md 5.6 KB
- reference/SSC-EWI-0002.md 3.2 KB
- reference/SSC-EWI-0021.md 6.7 KB
- reference/SSC-EWI-0030.md 7.5 KB
- reference/SSC-EWI-0040.md 5.0 KB
- reference/SSC-EWI-0056.md 5.2 KB
- reference/SSC-EWI-0058.md 7.0 KB
- reference/SSC-EWI-0073.md 1.2 KB
- reference/SSC-EWI-0108.md 3.6 KB
- reference/SSC-EWI-TS0075.md 8.6 KB
- reference/SSC-EWI-TS0083.md 10 KB
- reference/SSC-EWI-TS0087.md 22 KB
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 · 78 lines · 75 tokens per session scan A b46f2affe121
resolving-ewis is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 511 once invoked, about $0.0004 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 skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.