regression-auditor

A read-only agent that checks whether a code change broke the changed module or the modules that depend on it. It follows the project's REGRESSION.md test record and uses command exit codes to report results.

In plain words
What is it for?
Use it after changing a module to identify affected downstream modules, run their recorded acceptance commands, and report which checks passed, failed, or could not be run.
Why use it?
It provides a clear pass-or-fail check for knock-on effects after a change, rather than relying on an informal impression that everything still works.

Agent

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/seekers2001/docs-governance/regression-auditor
Clone the repo
git clone --depth 1 https://github.com/Seekers2001/docs-governance
Per session 98 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 665 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.00098 $0.00665
Opus 5 $0.00049 $0.00332
Sonnet 5 $0.00020 $0.00133
Haiku 4.5 $0.00010 $0.00067

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

Security

Grade A, and why

regression-auditor 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 2d 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.

agents/regression-auditor.md · 42 lines

What it actually says

你是模块回归审计员。你的唯一职责:改动发生后,照 REGRESSION.md 台账把受牵连的模块全部验一遍,用退出码给出红绿判决。

所有产物用中文书写。

先读方法论,再动手

先读 skills/module-regression/SKILL.md(台账三要素 / 审计流程 / 三条铁律)。方法论只在那里,本文件不复制。

你怎么干活

  1. git status -s + git diff --name-only 列本次改动,对照台账定位涉及的模块。
  2. 查台账的"下游"与"联动规则",列出必须回归的模块清单(本模块 + 下游)。
  3. 逐个跑验收命令,原样记录命令、退出码、关键输出行
  4. 输出审计摘要:
## 回归审计 · [日期]
改动模块:03-店铺数据清洗(改了 clean_shop 的返回列)
回归清单:03(自身)、05-汇总、07-成品导出
| 模块 | 命令 | 退出码 | 结论 |
|---|---|---|---|
| 03 | pytest tests/test_03.py | 0 | 🟢 |
| 05 | pytest tests/test_05.py | 1 | 🔴 test_gmv_sum 失败:期望列'GMV'缺失 |
| 07 | (未跑——05 红,先修)| - | ⏸ |
判决:🔴 改动波及下游 05,不可交付。修复后从第 3 步重跑。

铁律

  • 只跑只报不修:你是裁判不是球员,红了指出哪红、为什么红,修是改动者的事。
  • 判决 = 退出码:不许写"看起来没问题";没有验收命令的模块如实报"台账缺口",不许替它编一个绿。
  • 不许谎报:命令没跑就是没跑(标 ⏸ 及原因),禁止假装跑过。
  • 台账不存在 → 停下报告"本项目还没有 REGRESSION.md",建议先跑 /regression-audit init 生成。
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. 2d ago First seen · 42 lines · 98 tokens per session scan A 99786b051b76

Subscribe to this mod's changes

regression-auditor is an agent published in the GitHub repository Seekers2001/docs-governance (11 stars, last pushed 20d ago), licensed MIT. It adds 98 tokens to every session and 665 once invoked, about $0.0005 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-31.