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.
git clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/check-pipeline)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/check-pipeline"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/check-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.
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/check-pipeline"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/check-pipeline.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.00008 | $0.00241 |
| Opus 5.5 | $0.00003 | $0.00096 |
| Sonnet 5.5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
check-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.
What it actually says
Check Pipeline
Analyze CI/CD pipeline configuration and suggest improvements.
Your Task
Review pipeline configuration and provide optimization recommendations.
Arguments
$1: Pipeline configuration file (e.g., .github/workflows/ci.yml, .gitlab-ci.yml)
Steps
- Read pipeline configuration
- Check for common issues:
- No caching
- Sequential jobs that could be parallel
- Large Docker images
- Missing health checks
- No rollback strategy
- Provide recommendations:
- Add dependency caching
- Parallelize independent jobs
- Use multi-stage Docker builds
- Implement health checks
- Add automated rollbacks
- Estimate improvements:
- Build time reduction
- Reliability improvements
- Cost savings
Examples
/check-pipeline .github/workflows/ci.yml
Notes
- Focus on build speed and reliability
- Suggest specific code changes
- Prioritize high-impact optimizations
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.
- 1mo ago First seen · 50 lines · 8 tokens per session scan A 5313d05fd2fc
check-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 241 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.
Other commands, from other repositories
ci-readout
Generate a comprehensive summary of recent CI runs and failing jobs.
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.
release-check
Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
trace-regression
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
speckit.superspec.brainstorm
../../.opencode/commands/speckit.superspec.brainstorm.md.