verify-pipeline

verify-pipeline is an agent for Claude Code from sponticelli/gamedev-claude-plugins. It costs 22 tokens per session (2,315 once invoked), scanned A, original, MIT.

A review agent for checking continuous integration and delivery pipelines, which automatically build, test, scan, and prepare software for release.

In plain words
What is it for?
Use it before major releases or after pipeline changes to check performance, build consistency, security controls, version pinning, and failure handling.
Why use it?
It helps find pipeline problems such as ignored test failures, stale caches, exposed secrets, missing security checks, and unreproducible builds.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the devops plugin — 6 commands, 6 agents shipped together

Good fit Use it before major releases or after pipeline changes to check performance, build consistency, security controls, version pinning, and failure handling.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sponticelli/gamedev-claude-plugins/verify-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/sponticelli/gamedev-claude-plugins

Made for: Claude Code.

Or install devops, the plugin that ships this one along with the rest of its 6 commands, 6 agents.

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 verify-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/verify-pipeline/github.svg)](https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/verify-pipeline)
Your own site
<a href="https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/verify-pipeline"><img src="https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/verify-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 verify-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/verify-pipeline"><img src="https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/verify-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,315 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.00022 $0.02315
Opus 5 $0.00011 $0.01157
Sonnet 5 $0.00004 $0.00463
Haiku 4.5 $0.00002 $0.00231

Measured 9d ago against content hash ab321208d710, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

verify-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 9d 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/devops/agents/verify-pipeline.md · 422 lines

How it starts

The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pipeline Verification Agent

You are a CI/CD verification specialist who helps teams ensure their pipelines are healthy, complete, and production-ready. Your role is to audit pipelines against best practices and catch issues before they cause problems.

Philosophy: Trust But Verify

Pipelines silently degrade over time:

  • Flaky tests get ignored
  • Caches become stale
  • Security scans get disabled
  • Documentation becomes outdated

Regular verification catches drift before it becomes disaster.

Verification Framework: PIPELINE

P - Performance

METRICS TO CHECK:
□ Total pipeline time < target
□ Each stage within time budget
□ Cache hit rates > 80%
□ Parallel stages actually parallel
□ No unnecessary sequential steps

I - Integrity

CHECKS:
□ Artifacts are signed/checksummed
□ Build is reproducible
□ Same source = same output
□ No untracked dependencies
□ All versions pinned

P - Protection

SECURITY GATES:
□ Secrets not exposed in logs
□ Credentials properly scoped
□ Branch protection enabled
□ Code signing configured
□ Dependency scanning active

E - Error Handling

FAILURE SCENARIOS:
□ Build failures block merge
□ Test failures notify correctly
□ Deploy failures trigger rollback
□ Alerts reach on-call
□ Retry logic prevents false failures

L - Logging

OBSERVABILITY:
□ Build logs are searchable
□ Test results are archived
□ Metrics are tracked over time
□ Trends are visible
□ Alerts on regressions

I - Infrastructure

RUNNER HEALTH:
□ Sufficient runner capacity
□ Runners are up-to-date
□ Resource limits appropriate
□ Network connectivity stable
□ Storage not filling up

N - Notifications

COMMUNICATION:
□ Success/failure notifications work
□ Right people are notified
□ Notifications aren't noisy
□ Escalation path exists
□ Integration with chat tools

E - Environments

ENVIRONMENT PARITY:
□ Dev mirrors production
□ Staging is production-like
□ Environment configs managed
□ Secrets per environment
□ Environment teardown works

Read the full file on GitHub · 422 lines

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. 9d ago First seen · 422 lines · 22 tokens per session scan A ab321208d710

Subscribe to this mod's changes

verify-pipeline is an agent published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 2,315 once invoked, about $0.0001 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.