Borrowing it
Nothing to install: this file belongs to zapat-ai/zapat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zapat-ai/zapat/main/.claude/commands/pipeline-check.mdgit clone --depth 1 https://github.com/zapat-ai/zapatWrote 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/zapat-ai/zapat/pipeline-check)<a href="https://agentmods.dev/commands/zapat-ai/zapat/pipeline-check"><img src="https://agentmods.dev/badge/commands/zapat-ai/zapat/pipeline-check/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/commands/zapat-ai/zapat/pipeline-check"><img src="https://agentmods.dev/badge/commands/zapat-ai/zapat/pipeline-check.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.00000 | $0.00369 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
pipeline-check 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.
What it actually says
Pipeline Health Check
Run a quick health check on the Zapat pipeline and report results conversationally.
Steps
-
Run pipeline status:
bin/zapat statusSummarize the output: how many active sessions, recent job success rate, any items in progress.
-
Run health checks:
bin/zapat healthSummarize each check result. For any failures, explain what the issue means in plain language.
-
If any health checks failed, suggest fixes:
- tmux-session failed: "The tmux session is missing. Run
bin/startup.shto recreate it." - orphaned-worktrees: "There are leftover git worktrees from crashed sessions. Run
bin/zapat health --auto-fixto clean them up." - stale-slots: "Some agent slot files are stale (the process died). Run
bin/zapat health --auto-fixto reclaim them." - gh-auth failed: "GitHub CLI is not authenticated. Run
gh auth loginto fix." - failed-items: "Some items failed processing. Check the logs with
ls -lt logs/and review the most recent failure." - cron-job missing: "The cron job is not installed. Run
bin/startup.shto set it up."
- tmux-session failed: "The tmux session is missing. Run
-
If all checks pass, say something like: "Pipeline is healthy. All checks passed. [N] sessions active, [X]% success rate over the last 24 hours."
-
Ask if they want to run auto-fix for any issues:
bin/zapat health --auto-fix
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 · 34 lines · 0 tokens per session scan A a44d273f3823
pipeline-check is a command published in the GitHub repository zapat-ai/zapat (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 369 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-30.
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.