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 vaquarkhan/data-engineering-agent-skills --skill pipeline-planning-and-task-breakdowngit 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/skills/vaquarkhan/data-engineering-agent-skills/pipeline-planning-and-task-breakdown)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/pipeline-planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/pipeline-planning-and-task-breakdown/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/vaquarkhan/data-engineering-agent-skills/pipeline-planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/pipeline-planning-and-task-breakdown.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.00040 | $0.00546 |
| Opus 5 | $0.00020 | $0.00273 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
pipeline-planning-and-task-breakdown 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Planning And Task Breakdown
Overview
Turn a validated data specification into a sequence of small tasks that can be implemented and verified independently. A good plan protects the team from wide, risky pipeline edits.
When to Use
- multi-step ingestion or modeling work
- changes involving orchestration, infrastructure, and transformations
- work that needs coordination across contracts, checks, and deployment
Do not use this when the task is a single isolated change with obvious verification.
Workflow
-
Map the affected layers. Typical layers include:
- source connections
- raw landing
- staging transformations
- business models
- orchestration
- tests and checks
- documentation and runbooks
-
Order work by dependency. Good sequence:
- contracts
- scaffolding
- ingestion
- transformations
- checks
- orchestration
- rollout and recovery notes
-
Keep tasks small. Each task should:
- have one clear outcome
- touch a limited set of files
- define how it will be verified
- avoid mixing unrelated concerns
-
Call out risk points. Always identify:
- schema evolution risk
- backfill risk
- cost or performance risk
- downstream compatibility risk
-
Define evidence for every task. Examples:
- test results
- contract validation output
- successful dry run
- row count reconciliation
- lineage or docs update
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "It is faster to change everything in one pass." | Wide changes increase blast radius and make rollback harder. |
| "We can skip task boundaries because the repo is small." | Data dependencies, not repo size, create risk. |
| "The orchestrator wiring can wait until the end." | Scheduling and retry behavior often shape the implementation. |
Red Flags
- a single task spans ingestion, modeling, orchestration, and rollout
- verification says only "run the pipeline"
- rollback or compatibility concerns are not mentioned
- the plan does not separate build work from publish work
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.
- 9d ago First seen · 85 lines · 40 tokens per session scan A 703ff2bd6330
pipeline-planning-and-task-breakdown is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 546 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
kafka-shadowtraffic
Generate a ShadowTraffic configuration to populate a Kafka topic with realistic synthetic data. Discovers the target topic, its key and value schemas, and the correct serializers from the live cluster via any attached Kafka MCP server, then writes a ready-to-run shadowtraffic-config.json and Docker command. Use when…
kafka-shadowtraffic-java
Generate a TestContainers Java test class that spins up ShadowTraffic in-process to populate a Kafka topic with synthetic data during tests. Invokes the kafka-shadowtraffic skill to build the ShadowTraffic config, then adapts it for a containerized test network and scaffolds a JUnit 5 test class with Kafka, optional…
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…
kafka-consumer-lag
Analyse Kafka consumer group lag using the Lenses MCP server. Diagnoses lag causes (throughput bottlenecks, rebalancing, partition skew, stalled consumers) and suggests remediation. Use when user says "check consumer lag", "why are consumers slow", "lag report" or asks about consumer group health or offset progress.…
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-perf-review
Review Kafka producer and consumer performance configurations in both the live cluster (via Lenses MCP) and the codebase. Flags un-tuned defaults, anti-patterns and missing best practices. Use when user says "review Kafka performance", "check producer configs", "tune Kafka settings" or asks about throughput, batching…