validate-pipeline

validate-pipeline is a command for Claude Code from armanzeroeight/fastagent-plugins. It costs 8 tokens per session (191 once invoked), scanned A, original, MIT.

A command for reviewing a data pipeline, which is a sequence that moves and transforms data. It checks the pipeline setup, error handling, retries, monitoring, data checks, and idempotency, meaning safe repeated runs.

In plain words
What is it for?
Use it to review a pipeline file and get specific suggestions for error recovery, retries, monitoring, data-quality checks, and safe reruns.
Why use it?
It exposes reliability gaps that could cause failed jobs, bad data, missing alerts, or duplicated results.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to review a pipeline file and get specific suggestions for error recovery, retries, monitoring, data-quality checks, and safe reruns.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/armanzeroeight/fastagent-plugins/validate-pipeline
Install

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.

Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code.

Wrote 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.

agentmods badge for validate-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/validate-pipeline/github.svg)](https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/validate-pipeline)
Your own site
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/validate-pipeline"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/validate-pipeline/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.

agentmods 80×15 button for validate-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/validate-pipeline"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/validate-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.00191
Opus 5.5 $0.00003 $0.00076
Sonnet 5.5 $0.00002 $0.00038
Haiku 4.5 $0.00001 $0.00019

Measured 1mo ago against content hash db62242d9f82, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-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 1mo 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.

plugins/data-engineer/commands/validate-pipeline.md · 45 lines

What it actually says

Validate Pipeline

Validate data pipeline configuration and suggest improvements.

Your Task

Review pipeline configuration and data quality checks.

Arguments

  • $1: Pipeline configuration file (e.g., dags/etl_pipeline.py)

Steps

  1. Read pipeline configuration
  2. Check for:
    • Error handling
    • Retry logic
    • Monitoring
    • Data quality checks
    • Idempotency
  3. Provide recommendations:
    • Add missing error handling
    • Implement data quality checks
    • Add monitoring and alerts
    • Ensure idempotent operations

Examples

/validate-pipeline dags/etl_pipeline.py

Notes

  • Focus on reliability and data quality
  • Suggest specific improvements
  • Check for best practices
Changes

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.

  1. 1mo ago First seen · 45 lines · 8 tokens per session scan A db62242d9f82

Subscribe to this mod's changes

validate-pipeline is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 191 once invoked, about $0.0000 per session on Opus 5.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.