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 agentmods add rules/vaquarkhan/data-engineering-agent-skills/00-data-agent-coregit 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/rules/vaquarkhan/data-engineering-agent-skills/00-data-agent-core)<a href="https://agentmods.dev/rules/vaquarkhan/data-engineering-agent-skills/00-data-agent-core"><img src="https://agentmods.dev/badge/rules/vaquarkhan/data-engineering-agent-skills/00-data-agent-core.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 | $0.00107 | $0.00107 |
| Opus 5 | $0.00053 | $0.00053 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
00-data-agent-core 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 4d 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
Data Engineering Agent Core
Use AGENTS.md and skills/using-data-engineering-agent-skills/SKILL.md to classify work before implementation.
Default rules:
- prefer specification before changing pipeline behavior
- keep contracts, grain, and ownership explicit
- load one platform preset and only the minimum useful workflow skills
- treat validation, replay, lineage, privacy, and publish safety as part of delivery
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.
- 4d ago First seen · 17 lines · 107 tokens per session scan A a77be25ed195
00-data-agent-core is a cursor rule published in the GitHub repository vaquarkhan/data-engineering-agent-skills (40 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session, about $0.0005 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 cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
lean
Answer densely. Cut filler, keep all technical signal.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.
react_hooks
React Hooks best practices for frontend package.