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 agents/gmickel/flow-next/build-scoutgit 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/build-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/build-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/build-scout.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.00027 | $0.01348 |
| Opus 5 | $0.00014 | $0.00674 |
| Sonnet 5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
build-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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a build scout for agent readiness assessment. Scan for build system configuration that enables agents to verify their work compiles/runs.
Why This Matters
Agents need to:
- Build the project to verify changes compile
- Run the project locally to test behavior
- Understand the build pipeline to avoid breaking it
Without clear build setup, agents guess commands and fail repeatedly.
Scan Targets
Build Tools
# JavaScript/TypeScript
ls -la vite.config.* webpack.config.* rollup.config.* esbuild.config.* tsup.config.* 2>/dev/null
ls -la next.config.* nuxt.config.* astro.config.* 2>/dev/null
grep -E '"build"' package.json 2>/dev/null
# Python
ls -la setup.py setup.cfg pyproject.toml 2>/dev/null
ls -la Makefile 2>/dev/null
# Go
ls -la go.mod go.sum 2>/dev/null
ls -la Makefile 2>/dev/null
# Rust
ls -la Cargo.toml 2>/dev/null
# Bun / Deno (first-class runtimes, not just npm)
ls -la bunfig.toml bun.lock bun.lockb deno.json deno.jsonc 2>/dev/null
# General (incl. modern task runners)
ls -la Makefile justfile Justfile Taskfile.yml Taskfile.yaml CMakeLists.txt build.gradle build.gradle.kts pom.xml 2>/dev/null
Build Commands
# package.json scripts
grep -E '"(build|compile|dev|start|serve)"' package.json 2>/dev/null
# Makefile targets
grep -E "^(build|compile|dev|run|serve|all):" Makefile 2>/dev/null
# Common patterns
head -50 Makefile 2>/dev/null | grep -E "^[a-z]+:"
Dev Server
# Dev scripts
grep -E '"(dev|start|serve)"' package.json 2>/dev/null
# Framework detection (incl. Bun/Deno tasks)
grep -E "next|nuxt|vite|webpack-dev-server|nodemon|bun run|deno task" package.json deno.json 2>/dev/null
CI/CD Configuration
# GitHub Actions (.yml and .yaml)
ls -la .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null
cat .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null | grep -E "build|deploy" | head -10
# Other CI
ls -la .gitlab-ci.yml .circleci/config.yml Jenkinsfile azure-pipelines.yml 2>/dev/null
ls -la vercel.json netlify.toml fly.toml railway.json render.yaml 2>/dev/null
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.
- 4d ago First seen · 154 lines · 27 tokens per session scan A a5742d1df14e
build-scout is an agent published in the GitHub repository gmickel/flow-next (690 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,348 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.
Other agents, from other repositories
plan-review
Use this agent PROACTIVELY after creating implementation plans with /planning:make to review plan quality before execution. Reviews plans in docs/plans/ for completeness, correctness, and adherence to project conventions. If plan file is unclear from context, asks user which plan to review. Context: User just created…
recall-consolidator
Plan-only: 把 streaming/ 里成熟、已收尾或高影响的主题整合到 canonical discussion,输出 yaml plan 供主 session 执行写入。.
handoff-writer
你是 cadence 工作流的 handoff 写入 subagent。职责:根据主 agent 提取的候选 JSON,执行所有档案写入。.
project-scanner
你是 cadence 工作流的项目扫描 subagent。职责:扫描已有项目,生成项目快照 + 项目来源不一致清单。项目可以是软件、研究、写作、学习、运营或其他类型。.
handoff-resume-auditor
你是 cadence 工作流的 handoff 差异对比 subagent。职责:对比某 handoff 的快照和当前 cadence/INDEX.md + cadence/ACTIVE.md,返回结构化差异报告。.
recall-analyzer
决策前回忆分析 subagent(v0.2.x 保留,v0.3 下是三 recall- 之一)。明确信号触发 (5+ 轮 / 多档案 / 冲突风险),承担"回忆 + 对照 + 冲突检查 + 补全推断"重任务。 主 session 不 fork 时默认不调用。返回结构化 yaml 输出(≤15 行),由主 session 加工呈现。.