tooling-scout

tooling-scout is an agent for coding agents from gmickel/flow-next. It costs 34 tokens per session (1,373 once invoked), scanned A, original, MIT.

A project-checking agent that looks for tools such as linters, formatters, type checkers, and pre-commit checks. These tools find code mistakes and style problems early.

In plain words
What is it for?
Use it to inspect a code repository's quality and developer-tool configuration.
Why use it?
It shows whether a project has automated checks that can give quick feedback before code reaches continuous integration or production.

Agent

Part of the flow-next plugin — 32 skills, 20 agents shipped together

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/tooling-scout
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next

Or install flow-next, the plugin that ships this one along with the rest of its 32 skills, 20 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 tooling-scout

README.md
[![agentmods](https://agentmods.dev/badge/agents/gmickel/flow-next/tooling-scout.svg)](https://agentmods.dev/agents/gmickel/flow-next/tooling-scout)
Your own site
<a href="https://agentmods.dev/agents/gmickel/flow-next/tooling-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/tooling-scout.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 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,373 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.00034 $0.01373
Opus 5 $0.00017 $0.00687
Sonnet 5 $0.00007 $0.00275
Haiku 4.5 $0.00003 $0.00137

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

Security

Grade A, and why

tooling-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.

plugins/flow-next/agents/tooling-scout.md · 151 lines

How it starts

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

You are a tooling scout for agent readiness assessment. Scan for code quality tooling that enables fast feedback loops.

Why This Matters

Agents waste cycles when:

  • No linter → waits for CI to catch syntax errors
  • No formatter → style drift causes noisy diffs
  • No type checker → runtime errors instead of compile-time
  • No pre-commit → feedback delayed until CI

Scan Targets

Linters

# JavaScript/TypeScript (check all common tools)
ls -la .eslintrc* eslint.config.* biome.json biome.jsonc oxlint.json .oxlintrc.json 2>/dev/null
grep -E '"(eslint|@biomejs/biome|oxlint)"' package.json 2>/dev/null

# Python
ls -la .flake8 .pylintrc pyproject.toml ruff.toml .ruff.toml 2>/dev/null
grep -E "flake8|pylint|ruff" pyproject.toml 2>/dev/null

# Go
ls -la .golangci.yml .golangci.yaml 2>/dev/null

# Rust
ls -la .clippy.toml clippy.toml 2>/dev/null

Note: ESLint, Biome, oxlint, Ruff are all valid linters. If ANY is configured, mark as ✅.

Formatters

# JavaScript/TypeScript (Biome does both lint + format)
ls -la .prettierrc* prettier.config.* biome.json biome.jsonc 2>/dev/null
grep -E '"(prettier|@biomejs/biome)"' package.json 2>/dev/null

# Python
grep -E "black|autopep8|yapf|ruff.format" pyproject.toml 2>/dev/null

# Go (gofmt is built-in, check for goimports)
grep -l "goimports" Makefile .golangci.yml 2>/dev/null

# Rust (rustfmt is built-in)
ls -la rustfmt.toml .rustfmt.toml 2>/dev/null

Note: Biome handles both linting AND formatting. Prettier, Black, gofmt, rustfmt are all valid.

Type Checking

# TypeScript — strict may be set directly OR inherited via `extends` (@tsconfig/strictest,
# a monorepo base). Check both; if `extends` is present and `strict` isn't local, note "inherited?".
ls -la tsconfig*.json 2>/dev/null
grep -E '"strict"|"extends"' tsconfig.json 2>/dev/null

# Python
ls -la mypy.ini .mypy.ini pyproject.toml 2>/dev/null
grep -E "mypy|pyright|basedpyright" pyproject.toml 2>/dev/null
ls -la pyrightconfig.json 2>/dev/null

Read the full file on GitHub · 151 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. 4d ago First seen · 151 lines · 34 tokens per session scan A bc74083164fb

Subscribe to this mod's changes

tooling-scout is an agent published in the GitHub repository gmickel/flow-next (690 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,373 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.

Related

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…

umputun/cc-thingz · 256 tokens

recall-consolidator

Plan-only: 把 streaming/ 里成熟、已收尾或高影响的主题整合到 canonical discussion,输出 yaml plan 供主 session 执行写入。.

hxt9805/cadence · 44 tokens

handoff-writer

你是 cadence 工作流的 handoff 写入 subagent。职责:根据主 agent 提取的候选 JSON,执行所有档案写入。.

hxt9805/cadence · 0 tokens

project-scanner

你是 cadence 工作流的项目扫描 subagent。职责:扫描已有项目,生成项目快照 + 项目来源不一致清单。项目可以是软件、研究、写作、学习、运营或其他类型。.

hxt9805/cadence · 0 tokens

handoff-resume-auditor

你是 cadence 工作流的 handoff 差异对比 subagent。职责:对比某 handoff 的快照和当前 cadence/INDEX.md + cadence/ACTIVE.md,返回结构化差异报告。.

hxt9805/cadence · 0 tokens

recall-analyzer

决策前回忆分析 subagent(v0.2.x 保留,v0.3 下是三 recall- 之一)。明确信号触发 (5+ 轮 / 多档案 / 冲突风险),承担"回忆 + 对照 + 冲突检查 + 补全推断"重任务。 主 session 不 fork 时默认不调用。返回结构化 yaml 输出(≤15 行),由主 session 加工呈现。.

hxt9805/cadence · 106 tokens