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 skills/byx-darwin/gitflow-cli/gf-pipeline-analyzernpx skills add byx-darwin/gitflow-cli --skill gf-pipeline-analyzergit clone --depth 1 https://github.com/byx-darwin/gitflow-cliWrote 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/skills/byx-darwin/gitflow-cli/gf-pipeline-analyzer)<a href="https://agentmods.dev/skills/byx-darwin/gitflow-cli/gf-pipeline-analyzer"><img src="https://agentmods.dev/badge/skills/byx-darwin/gitflow-cli/gf-pipeline-analyzer.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.00073 | $0.01517 |
| Opus 5 | $0.00036 | $0.00758 |
| Sonnet 5 | $0.00015 | $0.00303 |
| Haiku 4.5 | $0.00007 | $0.00152 |
Grade A, and why
gf-pipeline-analyzer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf-pipeline-analyzer — CI/CD Pipeline Health Analyzer
Three-dimensional analysis: success-rate trends / failure patterns / duration distribution → report + prioritized improvement suggestions. Read-only: never triggers/reruns/cancels pipelines. Full params & report template: docs/references/gf-pipeline-analyzer-params.md
Report Output & Archiving
When persisted for audit trail (e.g. by gf-workflow Phase 4), save the report
to docs/pipeline-analysis-report-<YYYY-MM-DD>-<context>.md. Once
pipeline-analysis-report-*.md files under docs/ exceed 5, move all but the
5 most recent (ordered by the Issue/PR number embedded in the filename) into
docs/reports-archive/<YYYY>-Q<N>/, bucketed by each report's own date. See
docs/index.md → Reports Archive for the full policy.
CLI Requirement
MUST use gf CLI, NOT gh CLI.
| CLI | Scope | Platform Support |
|---|---|---|
gf |
This project | GitHub + GitLab + GitCode |
gh |
GitHub only | GitHub only |
Why: gf is the unified CLI for this project. Using gh breaks GitLab/GitCode compatibility.
Preconditions
gfinstalled:command -v gfgfauthenticated:gf auth status
Overview
Read-only analysis of three CI/CD health dimensions, with improvement suggestions sorted by priority.
Trigger Keywords
CN 流水线分析 CI失败 flaky test 耗时分析
EN pipeline health analyze flaky test CI slow success rate
CLI gf pipeline report --branch <B> --days <N>
When NOT to Use
| Scenario | Why Not | Use Instead |
|---|---|---|
| Retrying or retriggering failed pipelines | This skill is strictly read-only analysis | Use platform web UI |
| Modifying CI configuration files | This skill analyzes pipeline data, not edits config | Edit .github/workflows/ files directly |
| Running local pre-commit checks | This skill analyzes remote CI/CD pipelines, not local hooks | /gf-precommit for local pre-commit quality gates |
| Auto-creating Issues for failures | This skill reports findings only, never creates Issues | /gf-issue-create for manual Issue creation after analysis |
| Fixing flaky tests | This skill identifies flaky tests but never modifies code | /gf-workflow for implementing fixes |
| Running full quality gate checks | This skill focuses on CI/CD pipeline metrics, not code quality | /gf-quality for 6-gate quality verification |
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.
- yesterday Changed · +20 lines dda42e0c15eb
- 5d ago First seen · 129 lines · 73 tokens per session scan A c0f9b0f566f7
gf-pipeline-analyzer is a skill published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,517 once invoked, about $0.0004 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-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.