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 data-eng-testing-patternsgit 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/data-eng-testing-patterns)<a href="https://agentmods.dev/skills/justanesta/claude-code-resources/data-eng-testing-patterns"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/data-eng-testing-patterns/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/data-eng-testing-patterns"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/data-eng-testing-patterns.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.00067 | $0.02029 |
| Opus 5.5 | $0.00027 | $0.00812 |
| Sonnet 5.5 | $0.00013 | $0.00406 |
| Haiku 4.5 | $0.00007 | $0.00203 |
Grade A, and why
data-eng-testing-patterns 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Engineering Testing Patterns
Comprehensive testing strategies for data pipelines, SQL transformations, and data contracts.
Core Principles
- Test data, not just code - Validate row counts, schema shapes, value distributions, and business rules alongside logic
- Data contracts are boundaries - Every producer/consumer interface needs explicit schema and semantic contracts
- Idempotent test fixtures - Tests must create, validate, and tear down their own state without side effects
- Test at multiple granularities - Unit test individual transforms, integration test pipeline stages, end-to-end test full workflows
- Fail fast with clear diagnostics - Store test failures with sample rows so debugging does not require re-running the full pipeline
Unit Testing SQL Transforms
Use pytest with DuckDB to validate individual transformations in memory
import pytest
import pandas as pd
from sqlalchemy import create_engine, text
@pytest.fixture(scope="module")
def test_engine():
engine = create_engine("duckdb:///:memory:")
yield engine
engine.dispose()
@pytest.fixture
def seed_orders(test_engine):
df = pd.DataFrame({
"order_id": [1, 2, 3],
"customer_id": [101, 101, 102],
"amount": [50.00, 75.00, 200.00],
"status": ["completed", "completed", "refunded"],
})
df.to_sql("orders", test_engine, if_exists="replace", index=False)
return df
def test_revenue_excludes_refunds(test_engine, seed_orders):
result = pd.read_sql(text("""
SELECT customer_id, SUM(amount) AS total_revenue
FROM orders WHERE status != 'refunded'
GROUP BY customer_id
"""), test_engine)
assert len(result) == 1
assert result.iloc[0]["total_revenue"] == 125.00
See sql-transform-testing.md for:
- CTE isolation testing
- dbt unit test patterns with mock inputs
- Testing window functions and complex aggregations
- Snapshot and slowly changing dimension tests
What ships with it
5 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 · 250 lines · 67 tokens per session scan A 049dd6773650
data-eng-testing-patterns is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 6mo ago), licensed MIT. It adds 67 tokens to every session and 2,029 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
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
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…
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
Drizzle ORM Testing
Testing patterns for Drizzle ORM covering migration testing, query builder testing, transaction testing, and database integration testing with PostgreSQL, SQLite, and MySQL.
finance-weekly-outlook
Generate a source-backed weekly financial trading outlook from daily-finance, finance-core-analysis, and finance-explosive-article outputs plus fresh authoritative market data. Use when the user asks for future-one-week market outlook, weekly bullish/bearish sectors, stock picks, China A-share and US stock coverage…
postgres-commit-history-article
A workflow for comparing PostgreSQL source-code changes between two Git commits and, when useful, writing a Chinese Markdown article about them. PostgreSQL is a database system, and a commit is a saved change in a Git repository.