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/armanzeroeight/fastagent-plugins/validate-pipelinegit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWhat 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.00008 | $0.00191 |
| Opus 5 | $0.00004 | $0.00096 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 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.
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
- Read pipeline configuration
- Check for:
- Error handling
- Retry logic
- Monitoring
- Data quality checks
- Idempotency
- 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
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 · 45 lines · 8 tokens per session scan A db62242d9f82
validate-pipeline is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 191 once invoked, about $0.0000 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 commands, from other repositories
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
aidd-parallel
Generate /aidd-fix delegation prompts for a list of tasks and optionally dispatch them to sub-agents in dependency order.
aidd-pr
Review a PR, resolve addressed comments, and generate /aidd-fix delegation prompts for remaining issues.
OPSX: Sync
Sync delta specs from a change to main specs.