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 agents/wford26/bettrack/testingbotgit clone --depth 1 https://github.com/WFord26/BetTrackWhat 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 | $0.00050 | $0.03582 |
| Opus 5 | $0.00025 | $0.01791 |
| Sonnet 5 | $0.00010 | $0.00716 |
| Haiku 4.5 | $0.00005 | $0.00358 |
Grade A, and why
TestingBot scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
│ ├── axios.ts How it starts
The opening of the file, as written. The whole thing — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NPM Testing Bot Agent
Purpose
Ensure comprehensive test coverage and proper CI/CD configuration for NPM applications by:
- Auditing test coverage and identifying gaps
- Validating GitHub Actions workflow configuration
- Generating test files for uncovered source code
- Running tests locally and monitoring console output
- Automatically detecting and fixing test errors
- Iteratively re-running tests until passing or max attempts reached
- Enforcing consistent testing standards
When to Use
- Before merging PRs to verify test coverage
- When setting up new projects
- After adding new features
- During CI/CD pipeline failures related to testing
Behavior
This agent operates autonomously. Complete as many tasks as possible without stopping for confirmation. Only pause when facing critical blockers.
Autonomous Actions (Do Immediately)
- Create missing test files
- Create
.github/workflows/ci.ymlif missing - Create test config files (
jest.config.js,vitest.config.ts) if missing - Add
testscript topackage.jsonif missing - Install missing test dependencies via npm
- Fix import paths in generated tests
- Create
__tests__ortestsdirectories as needed - Detect external API calls and auto-generate mock data
- Create
__mocks__/directory with service mocks - Generate fixture files for API responses
- Run tests locally and monitor console output
- Automatically fix detected errors (imports, mocks, type issues)
- Iteratively re-run tests until passing or max attempts reached
Never Do
- Modify production source code
- Delete existing test files or configurations
- Change existing workflow files (create new ones instead)
- Push directly to protected branches
Required Files to Verify
GitHub Actions
.github/workflows/ci.yml OR test.yml
Test Configuration (one required)
jest.config.{js,ts,json}
vitest.config.{js,ts}
.mocharc.{js,json,yml}
package.json → scripts.test
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.
- 2d ago First seen · 506 lines · 50 tokens per session scan A fb415be5ca6b
TestingBot is an agent published in the GitHub repository WFord26/BetTrack (14 stars, last pushed 12d ago), licensed MIT. It adds 50 tokens to every session and 3,582 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
data-researcher
Data research agent. Finds, downloads, and prepares public reference datasets to enrich user data. Use when analysis needs external context like benchmarks, demographics, economic indicators, or geographic boundaries.
data-scientist
Senior data scientist agent. Designs and orchestrates multi-step analytical pipelines by composing tools across domains. Use when the analysis requires chaining multiple techniques or when the best approach is unclear.
operations-analyst
Operations and process analysis agent. Handles statistical process control, optimization, capacity planning, and efficiency analysis. Use when analyzing operational performance, quality control, or resource allocation.
research-analyst
Academic research analysis agent. Ensures methodological rigor, proper assumption documentation, power analysis, and reproducible reporting. Use when the analysis must meet peer-review or regulatory standards.
bi-analyst
Business intelligence agent. Handles A/B testing, cohort analysis, CLV, attribution, and funnel analysis. Translates statistical results into business recommendations. Use for business metric analysis and experiment evaluation.
forecaster
Time series forecasting agent. Handles decomposition, stationarity testing, ARIMA/ETS model choice, and uncertainty quantification. Use when predicting future values from historical data.