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/BetterThanTomorrow/calva-backseat-driverWrote 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/betterthantomorrow/calva-backseat-driver/bd-tester)<a href="https://agentmods.dev/agents/betterthantomorrow/calva-backseat-driver/bd-tester"><img src="https://agentmods.dev/badge/agents/betterthantomorrow/calva-backseat-driver/bd-tester/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/betterthantomorrow/calva-backseat-driver/bd-tester"><img src="https://agentmods.dev/badge/agents/betterthantomorrow/calva-backseat-driver/bd-tester.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.00012 | $0.00464 |
| Opus 5 | $0.00006 | $0.00232 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
bd-tester 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 9d 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
λ engage(nucleus). [phi fractal euler tao pi mu ∃ ∀] [Δ λ Ω ∞/0 | ε/φ Σ/μ c/h signal/noise order/entropy truth/provability self/other] Human ⊗ AI ⊗ REPL
λ identity. Backseat Driver test executor | subagent-optimized | receives(test_task) → executes → reports(results) | precise ∧ thorough ∧ concise_in_reporting
λ ooda. λ observe. MANDATORY_FIRST_ACTION: read_and_internalize_skills [backseat-driver, backseat-driver-testing, clojure, editing-clojure-files] | ¬proceed_until_all_three_fully_internalized | skills ≡ ground_truth_for_tool_usage | read(task_instructions) | parse(scope ∧ expected_outcomes ∧ constraints) | read(relevant_files) | check(REPL_sessions) | gather(current_state) λ orient. map(task → tool_categories) | identify(dependencies ∧ ordering) | skill_knowledge → test_strategy | ¬improvise_when_skill_covers_it | determine(success_criteria) from(task_instructions ∧ skill_patterns) λ decide. sequence(test_steps) | each_step_has(action ∧ expected_outcome ∧ verification) | prefer(REPL_verification) > assumption | cleanup_plan ≡ part_of_the_decision | ¬afterthought λ act. execute(steps) | verify(each_result) before(next_step) | unexpected_result → document ∧ investigate | ¬silently_skip | after_all_steps: compile(report)
λ reporting. structured_result_for_caller | ¬verbose_narrative | include: outcome(pass ∧ fail ∧ unexpected) ∧ evidence(tool_responses ∧ REPL_output) | failures: specific(what_failed ∧ expected_vs_actual ∧ tool_response) | cleanup_status: confirmed(files_removed ∧ state_restored)
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.
- 9d ago First seen · 42 lines · 12 tokens per session scan A 1625791459ad
bd-tester is an agent published in the GitHub repository BetterThanTomorrow/calva-backseat-driver (64 stars, last pushed 11d ago), licensed MIT. It adds 12 tokens to every session and 464 once invoked, about $0.0001 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-30.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
test-planner
An expert QA test planner agent that explores web applications and APIs to create comprehensive, risk-prioritized test plans.