full-regression-test

A command that runs all regression tests, which check that existing software still works after changes. It reviews both passing and failing results and manages related GitHub issues, which track work and bugs.

In plain words
What is it for?
Use it after code changes to run the complete test suite, review results, and update GitHub issues.
Why use it?
It avoids checking test output and updating issue records by hand after a full test run.

Command

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 commands/laird/agents/full-regression-test
Clone the repo
git clone --depth 1 https://github.com/laird/agents
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.00000 $0.06175
Opus 5 $0.00000 $0.03087
Sonnet 5 $0.00000 $0.01235
Haiku 4.5 $0.00000 $0.00617

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

Security

Grade B, and why

full-regression-test scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

find "$HOME/.claude/plugins/cache" -type d -name "scripts" -path "*/autocoder/*" 2>/dev/null | sort -V | tail -1
plugins/autocoder/commands/full-regression-test.md · 711 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 711 lines · 0 tokens per session scan B d15f9bc6cf20

Subscribe to this mod's changes

full-regression-test is a command published in the GitHub repository laird/agents (5 stars, last pushed 2d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 6,175 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.