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 file-and-partner-feed-ingestiongit 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/file-and-partner-feed-ingestion)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/file-and-partner-feed-ingestion"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/file-and-partner-feed-ingestion/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/file-and-partner-feed-ingestion"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/file-and-partner-feed-ingestion.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.00056 | $0.00671 |
| Opus 5 | $0.00028 | $0.00336 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
file-and-partner-feed-ingestion 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 12d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File And Partner Feed Ingestion
Overview
Use this skill when ingestion depends on externally delivered files rather than APIs or CDC streams. It helps agents design landing, validation, late-file handling, checksum or manifest controls, replay safety, and publish boundaries for partner-managed feeds.
When to Use
- onboarding
SFTP, MFT, or shared-bucket file feeds - ingesting recurring
CSV,JSON,XML, or columnar extracts from external partners - validating manifests, checksums, control totals, or arrival windows
- handling late, duplicate, partial, or corrected file deliveries
- defining replay-safe landing and publish behavior for externally supplied data
Do not assume file ingestion is simple just because the payload arrives in a batch.
Workflow
-
Define the feed contract. Clarify:
- file format and expected schema
- naming convention
- arrival schedule or SLA
- manifest, checksum, or control-total expectations
- ownership and contact path for the partner or source team
-
Design the landing boundary. Decide:
- where raw files land
- what metadata is captured
- how duplicates are detected
- how partial or corrupt deliveries are quarantined
-
Validate before publish. Include:
- schema and required-field checks
- checksum or manifest validation
- row-count or control-total validation
- late-file and missing-file detection
-
Make replay behavior explicit. Decide how:
- corrected files are handled
- duplicate files are ignored or reconciled
- replay windows are bounded
- downstream publishes stay protected until validation passes
-
Define failure and escalation behavior. Document:
- who gets alerted
- what blocks publish
- how the partner is contacted
- how recovery evidence is recorded
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "It is just a file drop." | File-based feeds often fail through late arrival, partial delivery, duplicate upload, or silent schema drift. |
| "We can validate after loading." | Weak landing controls let corrupt or incomplete partner data flow too far downstream. |
| "If the partner resends the file, we are fine." | Resends without replay-safe handling can create duplicate or conflicting publishes. |
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.
- 12d ago First seen · 83 lines · 56 tokens per session scan A e409d8dcbef3
file-and-partner-feed-ingestion is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 671 once invoked, about $0.0003 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 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-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-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-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-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…
kafka-schema-review
Review Kafka schema changes (Avro, Protobuf, JSON Schema) for compatibility and evolution best practices using the Lenses MCP server. Detects breaking changes, missing defaults, schema drift and naming issues. Use when user says "review schema changes", "check schema compatibility", "will this schema break consumers"…