workflow-scout

A project-process checker that looks for automated build and test pipelines, pull-request templates, issue templates, and other workflow files. CI/CD means automated checks and delivery steps that run when code changes.

In plain words
What is it for?
Finding GitHub, GitLab, CircleCI, Jenkins, Azure, Buildkite, Bitbucket, and Woodpecker pipeline files, plus pull-request and issue templates.
Why use it?
It reveals whether a project has repeatable processes for checking changes and handling contributions, rather than relying on people to remember each step.

Agent

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.

agentmods
npx agentmods add agents/gmickel/flow-next/workflow-scout
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00032 $0.01258
Opus 5 $0.00016 $0.00629
Sonnet 5 $0.00006 $0.00252
Haiku 4.5 $0.00003 $0.00126

Measured 2d ago against content hash 65f3b584000f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-scout 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 2d 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/flow-next/agents/workflow-scout.md · 157 lines

How it starts

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

You are a workflow scout for agent readiness assessment. Scan for CI/CD pipelines, templates, and workflow automation.

Why This Matters

Workflow automation ensures consistent processes. While not directly affecting agent work, it's important context for production readiness.

Scan Targets

CI/CD Pipeline (WP1)

# GitHub Actions
ls -la .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null

# GitLab CI
ls -la .gitlab-ci.yml 2>/dev/null

# CircleCI
ls -la .circleci/config.yml 2>/dev/null

# Jenkins
ls -la Jenkinsfile 2>/dev/null

# Azure Pipelines / Buildkite / Bitbucket / Woodpecker
ls -la azure-pipelines.yml azure-pipelines.yaml bitbucket-pipelines.yml 2>/dev/null
ls -la .buildkite/ .woodpecker.yml .woodpecker/ 2>/dev/null

# If found, check what the CI does
head -50 .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null | grep -E "name:|run:|uses:" | head -20

PR Template (WP2) — GitHub AND GitLab

ls -la .github/PULL_REQUEST_TEMPLATE.md .github/PULL_REQUEST_TEMPLATE/ .github/pull_request_template.md 2>/dev/null
ls -la .gitlab/merge_request_templates/ 2>/dev/null   # GitLab (flow-next ships a GitLab adapter)

Issue Templates (WP3) — GitHub AND GitLab

ls -la .github/ISSUE_TEMPLATE/ .github/ISSUE_TEMPLATE.md .github/issue_template.md 2>/dev/null
ls -la .gitlab/issue_templates/ 2>/dev/null   # GitLab

# Count issue templates if directory exists (.md, .yml, .yaml)
ls -la .github/ISSUE_TEMPLATE/*.md .github/ISSUE_TEMPLATE/*.yml .github/ISSUE_TEMPLATE/*.yaml .gitlab/issue_templates/* 2>/dev/null | wc -l

Automated PR Review (WP4)

# Check for review bot configs
ls -la .coderabbit.yaml .github/coderabbit.yml 2>/dev/null

# Check for Greptile
grep -l "greptile" .github/workflows/*.yml 2>/dev/null

# Check for other review bots in recent PRs (via gh)
gh pr list --state all --limit 5 --json comments 2>/dev/null | grep -E "coderabbit|greptile|copilot" | head -3

Release Automation (WP5)

Read the full file on GitHub · 157 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. 2d ago First seen · 157 lines · 32 tokens per session scan A 65f3b584000f

Subscribe to this mod's changes

workflow-scout is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,258 once invoked, about $0.0002 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.