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 commands/vaquarkhan/data-engineering-agent-skills/specgit 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/commands/vaquarkhan/data-engineering-agent-skills/spec)<a href="https://agentmods.dev/commands/vaquarkhan/data-engineering-agent-skills/spec"><img src="https://agentmods.dev/badge/commands/vaquarkhan/data-engineering-agent-skills/spec.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.00000 | $0.00072 |
| Opus 5 | $0.00000 | $0.00036 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
spec 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
/spec
Use skills/data-specification/SKILL.md and the templates in templates/ to define the data product before implementation.
Checklist:
- identify the business outcome
- identify source and destination contracts
- define grain, cadence, quality, privacy, and replay expectations
- list open questions instead of guessing
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 · 11 lines · 0 tokens per session scan A 3e5732e60b94
spec is a command published in the GitHub repository vaquarkhan/data-engineering-agent-skills (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 72 tokens. 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 commands, from other repositories
constraints
Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md.
define-agent-goal
Turn a rough task into an agent Goal (six core sections, 3 to 5 success criteria, helper goals when parallel, two-step approval); plan-only, no execution in the same turn.
setup-x402-client
Add x402 payment handling to a Node.js project using @dexterai/x402.
design-thinking
Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.
setup
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides).
gen
Automatically generates type definitions based on your Postgres database schema.