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 justanesta/claude-code-resources --skill sql-transformationsgit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWrote 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/justanesta/claude-code-resources/sql-transformations)<a href="https://agentmods.dev/skills/justanesta/claude-code-resources/sql-transformations"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/sql-transformations/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/justanesta/claude-code-resources/sql-transformations"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/sql-transformations.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.00068 | $0.01553 |
| Opus 5.5 | $0.00027 | $0.00621 |
| Sonnet 5.5 | $0.00014 | $0.00311 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
sql-transformations 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 2mo 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Transformations
Essential SQL patterns for ETL, data cleaning, and transformation workflows.
Core Principles
- Clean at the source - Fix data quality issues as early as possible
- Idempotent transformations - Same input always produces same output
- Document assumptions - Make data quality rules explicit
- Handle NULLs explicitly - Never assume NULL behavior
- Test transformations - Validate with sample data before production
Data Cleaning Strategies
WITH
valid_records AS (
SELECT * FROM raw_customer_data
WHERE email IS NOT NULL AND email LIKE '%@%'
),
standardized AS (
SELECT
customer_id,
TRIM(UPPER(email)) AS email,
CASE
WHEN UPPER(country) IN ('US', 'USA', 'UNITED STATES') THEN 'United States'
WHEN UPPER(country) IN ('UK', 'UNITED KINGDOM', 'GB') THEN 'United Kingdom'
ELSE INITCAP(TRIM(country))
END AS country,
REGEXP_REPLACE(phone, '[^0-9]', '', 'g') AS phone_digits_only
FROM valid_records
)
SELECT * FROM standardized;
See data-cleaning-patterns.md for:
- Validation rules and quality checks
- Standardization patterns and multi-stage pipelines
- Outlier detection and data quality scoring
Type Conversions
SELECT
-- Safe string to numeric
CASE
WHEN price_str ~ '^[0-9]+\.?[0-9]*$' THEN price_str::NUMERIC
ELSE NULL
END AS price,
-- Safe string to date
CASE
WHEN date_str ~ '^\d{4}-\d{2}-\d{2}$' THEN date_str::DATE
ELSE NULL
END AS order_date,
-- JSON extraction
(json_data->>'customer_id')::INTEGER AS customer_id
FROM staging_data;
See type-conversions.md for:
- Safe type casting patterns across databases
- JSON and array handling
- Cross-database conversion syntax
String Operations
SELECT
INITCAP(product_name) AS product_title_case,
LPAD(id::TEXT, 10, '0') AS id_padded,
SPLIT_PART(email, '@', 2) AS email_domain,
REGEXP_REPLACE(phone, '[^0-9]', '', 'g') AS phone_numbers_only,
CONCAT_WS(', ', city, state, country) AS location
FROM products;
What ships with it
6 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.
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.
- 2mo ago First seen · 207 lines · 68 tokens per session scan A 64b07b273ad0
sql-transformations is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 1,553 once invoked, about $0.0003 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-31.
Other skills, from other repositories
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
rag-pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
ingesting-into-data-lake
Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where…
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.