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 skills/benkapner/claude-code-basecamp/data-pipeline-patternsnpx skills add Benkapner/claude-code-basecamp --skill data-pipeline-patternsgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/benkapner/claude-code-basecamp/data-pipeline-patterns)<a href="https://agentmods.dev/skills/benkapner/claude-code-basecamp/data-pipeline-patterns"><img src="https://agentmods.dev/badge/skills/benkapner/claude-code-basecamp/data-pipeline-patterns.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.00036 | $0.00659 |
| Opus 5 | $0.00018 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
data-pipeline-patterns 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 3d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Pipeline Patterns — Team Conventions
Claude already knows validation, error handling, and retry patterns. This covers our team's specific stage structure and conventions.
When to Activate
- Building or modifying data pipeline stages
- Debugging pipeline failures (empty data, schema mismatches)
- Reviewing pipeline code
Standard Stage Structure
Every pipeline stage follows this pattern:
def main(argv=None):
args = parse_args(argv)
# 1. Load input
input_data = load_json_file(Path(args.file))
if input_data is None:
sys.exit(1)
# 2. Validate input
if not validate_json_structure(input_data, ["required_key"], "Input file"):
sys.exit(1)
# 3. Process
result = process(input_data)
# 4. Save output with metadata
output = {
"metadata": {
"source_file": str(args.file),
"generated_at": datetime.now().isoformat(),
"items_processed": len(result),
},
"data": result
}
save_json_file(output, output_path)
Key rules: Each stage is independently runnable (CLI + importable). Validate input before processing. Include metadata in every output. Fail fast on invalid input. Checkpoint every N items on long operations.
JSON Data File Conventions
- All output files:
metadatadict +data(list or dict) - Metadata always has:
source_file,generated_at, count fields - Use
_prefix for derived/computed fields - Dates as ISO 8601 strings (
2026-03-15T10:00:00) - Save with
indent=2andensure_ascii=False
Debugging Pipeline Failures
| Symptom | Likely Cause | Fix |
|---|---|---|
| Empty output file | Input had no matching items | Check filters, validate input data |
| Missing keys in output | Schema changed upstream | Update validation, check input stage |
| API timeout | Service overloaded or VPN down | Add retry logic, check connectivity |
| Rate limit errors (429) | Too many API calls | Add backoff, reduce batch size |
| Partial output | Stage crashed mid-processing | Add checkpointing |
| Wrong data types | API returned unexpected format | Add type validation at boundaries |
| Duplicate items | Pagination overlap | Deduplicate by key field |
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.
- 3d ago First seen · 79 lines · 36 tokens per session scan A e00ddd18c987
data-pipeline-patterns is a skill published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 14d ago), licensed MIT. It adds 36 tokens to every session and 659 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-08-30.
Other skills, from other repositories
data-science-python-stack
Opinionated Python stack for data-science / ML work — one library per job, organized into tiers (mandatory / user choice / optional / transitive). SKILL.md is the index; per-library references/ .md files carry scope, "pick this when" / "pick something else when", and pairings. TRIGGER when (any of these): (1) a…
mlops-industrialization
Convert notebook prototypes into a distributable Python package with a src layout, a domain/io/application split, and validated OmegaConf plus Pydantic configuration. Use when moving code out of notebooks or designing entrypoints.
tilelang-developer
Write, optimize, and debug high-performance AI compute kernels using TileLang (a Python DSL for GPU programming). Use when the user requests: (1) Writing custom GPU kernels for AI workloads (GEMM, Attention, MLA, etc.), (2) Optimizing existing TileLang code for NVIDIA, AMD, or Ascend hardware, (3) Implementing…
developing-genkit-python
Develop AI-powered applications using Genkit in Python. Use when the user asks about Genkit, AI agents, flows, or tools in Python, or when encountering Genkit errors, import issues, or API problems.
create-spring-boot-java-project
Skill "create-spring-boot-java-project" from boshi-xixixi/TraeSkill, covering create spring boot java project prompt, check java version, download spring boot project template, unzip the downloaded file and remove the downloaded zip file.
create-spring-boot-kotlin-project
Skill "create-spring-boot-kotlin-project" from boshi-xixixi/TraeSkill, covering create spring boot kotlin project prompt, check java version, download spring boot project template, unzip the downloaded file and remove the downloaded zip file.