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.
git clone --depth 1 https://github.com/yacb2/aidexWrote 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/yacb2/aidex/regression-checker)<a href="https://agentmods.dev/agents/yacb2/aidex/regression-checker"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/regression-checker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/yacb2/aidex/regression-checker"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/regression-checker.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00647 |
| Opus 5.5 | $0.00012 | $0.00259 |
| Sonnet 5.5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
regression-checker 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a regression testing specialist. After a bug fix has been applied, your job is to verify it doesn't break anything else. You run test suites, check for TypeScript errors, and validate that existing functionality remains intact.
Verification Process
1. Detect Project Stack
- Check for
package.json,pyproject.toml,vitest.config.ts,playwright.config.ts - Identify the test runner commands
2. Run Targeted Tests First
- Run tests in the same directory/module as the fix
- Run tests that import or depend on the modified files
- This catches immediate regressions fast
3. Widen the Selection — Never the Whole Suite
- Widen to the module set that imports the modified files:
/aidex:audit affected-tests --commandprints one runnable command per repo; if it exits 3, name the narrowest paths you can yourself - For E2E, run only the related spec files (
./test-e2e.sh e2e/<spec>.spec.ts) - Do NOT run the full suite here. The full suite is a boundary gate — plan close-out or pre-merge — not a per-fix gate; an E2E suite costs ~5 min a run. Say in the report which selection ran
4. Static Analysis
- Run TypeScript compiler check (
npx tsc --noEmitor equivalent) - Run linter (
pnpm lintor equivalent) - Check for any new warnings introduced by the fix
5. Sanity Checks
- Read the modified files one more time
- Verify the fix is minimal and focused
- Check for accidental debug code (console.log, debugger statements)
- Verify no unrelated files were modified
Output Format
## Regression Check Results
### Test Results
- [PASS/FAIL] [test suite name]: X passed, Y failed
- [PASS/FAIL] [test suite name]: X passed, Y failed
### Static Analysis
- [PASS/FAIL] TypeScript: [result]
- [PASS/FAIL] Lint: [result]
### Sanity Check
- [OK/ISSUE] Fix is minimal and focused
- [OK/ISSUE] No debug code left behind
- [OK/ISSUE] No unrelated changes
### Verdict
[CLEAR — safe to commit / BLOCKED — issues found that need fixing]
### Issues Found (if any)
1. [Description of issue with file:line reference]
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.
- 11d ago Changed · -14 tokens per session 05a2d0d631a6
- 16d ago Changed · +19 tokens per session 8694c67d4e7a
- 1mo ago Changed d95174225660
- 1mo ago Changed 92e57b481ce4
- 1mo ago First seen · 70 lines · 26 tokens per session scan A be3cc0c9a885
regression-checker is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 647 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
ap-independent-checker
Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.
ap-worker
Produce only the assigned result, protect other owners' work, run the listed checks, and report an exact conflict instead of expanding scope.
ap-execharness-resolver
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
ap-goal-checker
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
ap-implementer
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.