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/observability-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/observability-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/observability-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/observability-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.00034 | $0.01703 |
| Opus 5 | $0.00017 | $0.00851 |
| Sonnet 5 | $0.00007 | $0.00341 |
| Haiku 4.5 | $0.00003 | $0.00170 |
Grade A, and why
observability-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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an observability scout for agent readiness assessment. Scan for logging, tracing, metrics, and monitoring infrastructure.
Why This Matters
Observability helps debug issues in production. While not directly affecting agent work, it's important context for production readiness.
Scan Targets
Manifests recurse.
grep pkg */package.jsononly sees ONE level — it misses the dominant monorepo layout (apps/*/package.json,packages/*/package.json, deeper). Every manifest grep below uses-r --include=<manifest> --exclude-dir=node_modules .so it finds nested workspaces and never scans installed deps.
Structured Logging (OB1)
# JS/TS + Python + Go (recursive across workspaces, deps excluded)
grep -rE "winston|pino|bunyan|log4js" --include=package.json --exclude-dir=node_modules . 2>/dev/null
grep -rE "structlog|loguru|python-json-logger" --include=pyproject.toml --include=requirements*.txt --exclude-dir={.venv,node_modules} . 2>/dev/null
grep -rE "zap|logrus|zerolog|slog" --include=go.mod . 2>/dev/null
# Logging config files
find . -path '*/node_modules' -prune -o \( -name 'logback.xml' -o -name 'log4j*.xml' -o -name 'logging.config.*' \) -print 2>/dev/null | head
Distributed Tracing (OB2)
# OpenTelemetry across JS/Python/Go (Go OTel lives in go.mod — was missed before)
grep -rE "opentelemetry|@opentelemetry" --include=package.json --include=pyproject.toml --exclude-dir=node_modules . 2>/dev/null
grep -rE "go\.opentelemetry\.io" --include=go.mod . 2>/dev/null
# Trace ID propagation in OWN source (exclude deps — many HTTP libs mention these headers → false PASS)
grep -rE "X-Request-ID|X-Trace-ID|traceparent|correlation.id" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" --exclude-dir={node_modules,vendor,dist} . 2>/dev/null | head -10
Metrics Collection (OB3)
# Prometheus / Datadog / NewRelic / StatsD (recursive, deps excluded)
grep -rE "prom-client|prometheus|prometheus_client|prometheus/client" --include=package.json --include=pyproject.toml --include=go.mod --exclude-dir=node_modules . 2>/dev/null
grep -rE "dd-trace|datadog|ddtrace" --include=package.json --include=pyproject.toml --exclude-dir=node_modules . 2>/dev/null
grep -rE "newrelic|@newrelic" --include=package.json --include=pyproject.toml --exclude-dir=node_modules . 2>/dev/null
grep -rE "statsd|hot-shots" --include=package.json --exclude-dir=node_modules . 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 · 131 lines · 34 tokens per session scan A fc4080ab8272
observability-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,703 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.
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 加工呈现。.