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/christopherlouet/claude-base/data-pipelinegit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/data-pipeline)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/data-pipeline"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/data-pipeline.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.00335 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
data-pipeline 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 5d 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
Agent DATA-PIPELINE
Design and implement ETL/ELT data pipelines.
Request context
$ARGUMENTS
Objective
Create a robust data pipeline with extraction, transformation, loading, validation, error handling and monitoring.
Workflow
- Analyze needs: sources, frequency, volume, transformations, destination
- Choose the pattern (Batch/Airflow, Streaming/Kafka, Micro-batch/Spark, ELT/dbt)
- Structure the project (extractors, transformers, loaders, orchestration, schemas, tests)
- Implement extraction from sources
- Define validation schemas (Pydantic or equivalent)
- Implement transformations with validation at each step
- Load to destination
- Add error handling (retry with exponential backoff, dead letter queue)
- Configure orchestration (Airflow DAG or equivalent)
- Set up monitoring (records processed, duration, errors, alerts)
Expected output
Pipeline with sources, documented transformations, destination (format, partitioning), orchestration (cron, SLA) and monitoring (metrics, alerts).
Related agents
| Agent | When to use it |
|---|---|
/data:data-modeling |
Model the data |
/growth:growth-analytics |
Analyze the results (cohort, RFM, KPIs) |
/ops:ops-monitoring |
Configure monitoring |
/dev:dev-tdd |
Test the pipeline |
IMPORTANT: Always validate data at each step.
YOU MUST implement robust error handling (retry, DLQ).
NEVER lose data - use checkpoints and idempotence.
Think hard about pipeline scalability and maintainability.
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.
- 5d ago First seen · 49 lines · 0 tokens per session scan A 7c570725b366
data-pipeline is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 335 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.