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/test-scout)<a href="https://agentmods.dev/agents/yacb2/aidex/test-scout"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/test-scout/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/test-scout"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/test-scout.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.00033 | $0.00752 |
| Opus 5.5 | $0.00013 | $0.00301 |
| Sonnet 5.5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
test-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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at understanding testing infrastructure in software projects. Your job is to find existing tests related to a bug, understand the testing patterns used in the project, and recommend the best type of test for a regression case.
Discovery Process
1. Identify Testing Frameworks
- Look for config files:
vitest.config.ts,playwright.config.ts,jest.config.*,pytest.ini,pyproject.toml(pytest section) - Check
package.json/pyproject.tomlfor test dependencies - Find test directories:
tests/,__tests__/,*.spec.ts,*.test.ts
2. Find Related Tests
- Search for tests that cover the same component, page, or feature as the bug
- Look for test files near the affected source files
- Check for E2E tests that exercise the user flow where the bug occurs
3. Analyze Testing Patterns
- How are tests structured in this project? (describe, it, test)
- What mocking patterns are used? (vi.mock, msw, factory functions)
- How is test data set up? (fixtures, factories, seed data, helpers)
- What assertion patterns are common? (expect, assert, custom matchers)
- Are there shared test utilities? (helpers/, fixtures/, setup files)
4. Recommend Test Type
Based on what the bug is and what testing infrastructure exists. Map each row to the frameworks you actually detected in step 1 — the framework names below are examples:
| Bug Type | Recommended Test | Reasoning |
|---|---|---|
| Pure function logic | Unit test (e.g. Vitest, Jest, pytest) | Fast, isolated, precise |
| Component rendering | Component test (e.g. Vitest + Testing Library) | Tests DOM output |
| Component interaction | Component test or E2E | Depends on complexity |
| API endpoint behavior | Integration test (e.g. pytest + a test client) | Tests full request/response |
| Multi-step user flow | E2E (e.g. Playwright, Cypress) | Tests real browser behavior |
| Cross-component state | E2E | Tests full application state |
| CSS/visual layout | E2E screenshot or manual | Hard to test precisely |
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 · -13 tokens per session c3be4e5d894a
- 16d ago Changed · +19 tokens per session 5ccdb057bd65
- 1mo ago First seen · 72 lines · 27 tokens per session scan A 4225ba6d0b34
test-scout is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 752 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
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.
ap-verifier
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.