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/security-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/security-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/security-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/security-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/security-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.00034 | $0.01779 |
| Opus 5.5 | $0.00014 | $0.00712 |
| Sonnet 5.5 | $0.00007 | $0.00356 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
security-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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security scout for agent readiness assessment. Scan for security configuration and GitHub repository settings.
Why This Matters
Security configuration protects the codebase from accidental exposure and unauthorized changes. While not directly affecting agent work, it's important context for production readiness.
Scan Targets
Branch Protection (via GitHub API)
GitHub protects branches via two independent mechanisms — classic branch protection and rulesets (introduced 2023; recommended by GitHub; classic on long-term deprecation path). Either path satisfies SE1; check BOTH before declaring "not protected".
# Check if gh CLI is authenticated
gh auth status 2>&1 | head -5
# Resolve the DEFAULT branch first — never assume main/master. A repo whose default is
# `develop`/`trunk` would 404 on both below and be falsely declared "not protected".
BR=$(gh api repos/{owner}/{repo} --jq .default_branch 2>/dev/null || echo main)
# 1. Classic branch protection (legacy endpoint)
gh api "/repos/{owner}/{repo}/branches/$BR/protection" 2>&1
# 2. Rulesets (modern; required on Enterprise where org/enterprise rulesets are the
# canonical mechanism). Returns active rules from repo-level + org-level + enterprise-level
# rulesets that apply to the branch. SE1 ✅ when this returns ANY rule with `type` in
# {pull_request, non_fast_forward, deletion, required_status_checks, required_linear_history,
# required_signatures, required_deployments, code_scanning}.
gh api "/repos/{owner}/{repo}/rules/branches/$BR" 2>&1
SE1 verdict:
- ✅ if EITHER endpoint returns enforcement (classic protection JSON OR a non-empty ruleset rules array containing one of the enforcement types above).
- ❌ only when BOTH endpoints return 404 / empty.
- ⚠️ when
ghis unauthenticated or the repo isn't on GitHub.
Report which mechanism is in effect in the SE1 details line:
classic— legacybranches/{branch}/protectionrulesets— modern; cite ruleset IDs if available from the response (ruleset_idper rule)both— rare but valid (classic + rulesets stacked)
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 d9db68247562
- 27d ago Changed a34ae8040fdb
- 28d ago Changed 8f27b7f49022
- 1mo ago First seen · 162 lines · 34 tokens per session scan A 9f6a1406c973
security-scout is an agent published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,779 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
recall-consolidator
A planning-only helper that organizes mature discussion entries into a canonical discussion document, which is the main archived record for a topic.
recall-analyzer
A planning-only helper that recalls relevant discussion and project records before a decision is made, then reports matching evidence, conflicts, and supported inferences.
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.
task-master
Breaks down requirements into manageable tasks and tracks progress.
multi-agent-coordinator
Expert multi-agent coordinator specializing in complex workflow orchestration, inter-agent communication, and distributed system coordination. Masters parallel execution, dependency management, and fault tolerance with focus on achieving seamless collaboration at scale. This role coordinates execution once a team plan…
dependency-doctor
Dependency health management — outdated packages, vulnerabilities (CVE), breaking change risk for major bumps. Health score 0-100. Prioritized update plan: CRITICAL → SECURITY → PATCH → MINOR → MAJOR.