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/gmickel/flow-nextWrote 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/agents/gmickel/flow-next/workflow-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/workflow-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/workflow-scout/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/agents/gmickel/flow-next/workflow-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/workflow-scout.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.00032 | $0.01253 |
| Opus 5.5 | $0.00013 | $0.00501 |
| Sonnet 5.5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00125 |
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 13d 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.
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)
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.
- 13d ago Changed d50850ac3cbe
- 27d ago Changed 96e67795bf8d
- 28d ago Changed 0730c171ff32
- 1mo ago First seen · 157 lines · 32 tokens per session scan A 65f3b584000f
workflow-scout is an agent published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,253 once invoked, about $0.0001 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 agents, from other repositories
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
solve-issue
Problem-solving orchestrator. Guides users through clarifying a problem and then generating solutions with recommendations. Supports re-entry by passing a problem or solution file.
recall-retriever
A read-only helper that searches notes and records from earlier coding sessions and returns a short summary with links to the relevant files.
the-program-manager
Use for multi-team, multi-month technical program management—dependency mapping, risk gates per launch phase, orphaned cross-team problems, rollout plans with go/no-go criteria, status comms, escalations. Trigger when running a program (not a single-team feature), when an orphaned issue needs an owner, when planning a…
the-career-coach
Use when coaching individual contributors on career development, growth planning, and skill-building — promotion paths, skill gaps, role transitions. Distinct from report-career-architect (growth plans for the user's direct reports) and coaching-mode (ask-not-tell conversations). Helps ICs self-assess and build their…
the-retro-facilitator
Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (infrastructure postmortems) — this is the…