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 skills/bengous/claude-code-plugins/verify-no-regressionsnpx skills add bengous/claude-code-plugins --skill verify-no-regressionsgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/skills/bengous/claude-code-plugins/verify-no-regressions)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/verify-no-regressions"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/verify-no-regressions.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.1 | $0.00050 | $0.00579 |
| Opus 5 | $0.00025 | $0.00290 |
| Sonnet 5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
verify-no-regressions 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 6d 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.
What it actually says
Verify No Regressions
Usage: /verify-no-regressions [count] [base-branch] (defaults: 1 main)
Work state
- Working tree: !
git status --short 2>/dev/null || echo "(not a git repo)" - Commits ahead of base: !
set -- $ARGUMENTS; git log --oneline "${2:-main}"...HEAD 2>/dev/null || echo "(none or invalid base)" - Committed diff: !
set -- $ARGUMENTS; git diff --stat "${2:-main}"...HEAD 2>/dev/null - Staged diff: !
git diff --cached --stat 2>/dev/null - Unstaged diff: !
git diff --stat 2>/dev/null - Test scripts: !
cat package.json 2>/dev/null | jq -r '.scripts | to_entries[] | select(.key | test("test";"i")) | "\(.key): \(.value)"' 2>/dev/null || echo "(no package.json)"
Instructions
Read the work state above to determine what happened:
- Committed: commits ahead of base, clean working tree → review with
git diff base...HEAD - Staged: files in staging → review with
git diff --cached - Unstaged/untracked: modified or new files → review working tree files directly
- Mixed: combination of the above → review all layers
If nothing changed anywhere, report that and stop.
Spawn the subagents in a single message. Tell each agent which diff commands to use based on the work state.
-
Semantic reviewers (
model: opus-- judgment-heavy: intent, not syntax) -- split changed files across$0agent(s) (default: 1). Each agent:- Reads the diff (using the appropriate command for the work state) and current file contents
- Classifies each change as INTENTIONAL, RISKY (could break callers), or REGRESSION
- Reports verdict: PASS / NEEDS_REVIEW / FAIL
-
Test runner (
model: sonnet-- runs one command, reports a verdict; skip if no test infrastructure) -- one additional agent that runs the test suite and reports PASS / FAIL.
After all agents complete, synthesize a single report with overall verdict.
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.
- 6d ago First seen · 43 lines · 50 tokens per session scan A ab0914e8d3c0
verify-no-regressions is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 579 once invoked, about $0.0003 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.
Other skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
tencent-docs
腾讯文档(docs.qq.com)-在线云文档平台,是创建、编辑、管理文档的首选 skill。涉及"新建/创建/编辑/读取/查看/搜索文档"、"保存文件"、"云文档"、"腾讯文档"、"docs.qq.com"等操作,请优先使用本 skill。支持能力:(1) 创建各类在线文档(文档/Word/Excel/幻灯片/思维导图/流程图/智能表格/收集表)(2) 管理知识库空间(创建空间、查询空间列表)(3) 管理空间节点、文件夹结构 (4) 读取/搜索文档内容 (5) 编辑操作智能表 (6) 编辑操作在线文档 (7) 文件管理(重命名、移动、删除、复制、导入导出)(8) 网页剪藏、本地文件/文档上云。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:human-like-code-review
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
wechat-article-pro
微信公众号文章发布专业版。功能:1)联网搜索热点信息 2)AI生成微信公众号封面图 3)撰写3000-5000字深度文章 4)使用公众号AI配图功能自动生成并上传封面 5)参考刘润公众号风格写作 6)自动排版 7)不加话题标签.