Borrowing it
Nothing to install: this file belongs to vaquarkhan/data-engineering-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vaquarkhan/data-engineering-agent-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skillsWrote 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/instructions/vaquarkhan/data-engineering-agent-skills/claude-md)<a href="https://agentmods.dev/instructions/vaquarkhan/data-engineering-agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/vaquarkhan/data-engineering-agent-skills/claude-md.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.00700 | $0.00700 |
| Opus 5 | $0.00350 | $0.00350 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
data-engineering-agent-skills CLAUDE.md 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 7d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
data-engineering-agent-skills
This is the data-engineering-agent-skills project: a production-grade skill registry and execution toolkit for data engineering agents.
Project Structure
skills/ -> Core data engineering workflows (`SKILL.md` per directory)
presets/ -> Platform presets for AWS, Azure, GCP, Databricks, Snowflake, and Apache stacks
references/ -> Checklists for quality, recovery, streaming, schema change, observability, and more
templates/ -> Source, dataset, metric, and incident templates
starter-packs/ -> Opinionated bundles by problem area
examples/ -> Scenario packs: 5 runnable scaffolds + 9 architecture blueprints
hooks/ -> Session and pre-flight workflow hooks
.claude/commands/ -> Slash commands (`/spec`, `/plan`, `/build`, `/validate`, `/review`, `/backfill`, `/ship`)
.gemini/commands/ -> Gemini command entry points for the same lifecycle
docs/ -> Setup guides and getting-started documentation
vscode-extension/ -> VS Code family installer extension
jetbrains-plugin/ -> JetBrains installer plugin
Start Here
- Load
skills/using-data-engineering-agent-skills/SKILL.md - Load the platform preset that matches the stack
- Load only the task-specific skills needed for the current work
- Pull in references, templates, and examples only when they improve decisions or verification
Lifecycle Commands
/spec-> define contract, SLA, lineage, schema, retention, and ownership/plan-> break pipeline changes into atomic tasks/build-> implement pipeline, model, or job changes incrementally/validate-> prove data quality, contract compliance, and reconciliation/review-> review reliability, cost, governance, and operability/backfill-> run safe replay and cutover workflows/ship-> deploy, observe, and keep rollback-safe release notes
Conventions
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.
- 7d ago First seen · 62 lines · 700 tokens per session scan A f1ab60deacb3
data-engineering-agent-skills CLAUDE.md is an instructions file published in the GitHub repository vaquarkhan/data-engineering-agent-skills (40 stars, last pushed 2mo ago), licensed MIT. It adds 700 tokens to every session, about $0.0035 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-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.