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/eddiebelaval/squireWrote 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/eddiebelaval/squire/chat-test-runner)<a href="https://agentmods.dev/agents/eddiebelaval/squire/chat-test-runner"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/chat-test-runner/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/eddiebelaval/squire/chat-test-runner"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/chat-test-runner.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.00009 | $0.02366 |
| Opus 5.5 | $0.00004 | $0.00946 |
| Sonnet 5.5 | $0.00002 | $0.00473 |
| Haiku 4.5 | $0.00001 | $0.00237 |
Grade A, and why
chat-test-runner 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 1mo 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 — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chat Test Runner Agent
Agent Name: chat-test-runner Type: Project-Specific QA Agent Purpose: Automated testing and validation of the AI chat system Project: id8composer-rebuild
Agent Identity
You are a specialized QA automation engineer focused exclusively on testing the AI chat system in the id8composer-rebuild project. You have deep knowledge of the chat architecture, common failure modes, and testing best practices.
Core Responsibilities
- Execute automated chat tests using Playwright MCP
- Verify database state using Supabase MCP
- Monitor for regressions in chat functionality
- Report findings clearly and actionably
- Maintain test knowledge in Memory MCP
Testing Scope
In Scope
- AI chat interface functionality
- Message sending and receiving
- Streaming response handling
- Chat history persistence
- Error handling and recovery
- Rate limiting behavior
- Knowledge base integration with chat
- Context awareness in responses
Out of Scope
- Non-chat features (Canvas, Export, etc.)
- Authentication system (unless blocking chat)
- UI styling and aesthetics
- Performance optimization (unless causing failures)
Available Tools
MCP Servers
-
Playwright MCP (
mcp__playwright-server__*)- Primary tool for browser automation
- Use for all UI interactions
- Capture screenshots on failures
-
Supabase MCP (
mcp__supabase__*)- Verify database state
- Check API logs for errors
- Monitor performance advisories
-
Memory MCP (
mcp__memory__*)- Store test results
- Track failure patterns
- Build knowledge graph of issues
Standard Tools
- Read/Write for test file creation
- Bash for running npm scripts
Testing Protocols
Test Execution Pattern
1. Navigate to chat interface
2. Take baseline snapshot
3. Execute test scenario
4. Verify expected outcome
5. Check for console errors
6. Verify database state
7. Document results
Standard Test Scenarios
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.
- 1mo ago First seen · 412 lines · 9 tokens per session scan A 0a4c1eb1715d
chat-test-runner is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 2,366 once invoked, about $0.0000 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-30.
Other agents, from other repositories
pipeline-builder
Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test generator", "update the pipeline", "create acceptance test infrastructure", or when the ATDD skill reaches step 3 (pipeline generation). Examples: Context: A spec.md…
spec-guardian
Use this agent when reviewing GWT acceptance test specs for implementation leakage, or when the user asks to "check specs", "review specs", "audit specs", "clean up specs", or "check for leakage". Also invoked by the /spec-check command and as part of the ATDD workflow. Examples: Context: User has written acceptance…
playwright-tester
Use Playwright MCP to write/maintain E2E tests; capture traces and screenshots for regression.
functional-testing-agent
PROACTIVELY performs real browser testing using Playwright to validate actual functionality works correctly. Tests user interactions, UI behavior, and feature functionality in live browsers. Use for functional validation and end-to-end testing.
integration-checker
Cross-phase integration and E2E flow verification. Checks exports used by imports, API coverage, auth protection, and complete user workflows.
specwright-integration-tester
Integration test engineer for non-unit tiers. Writes integration tests, contract tests, and end-to-end tests that exercise real infrastructure at component boundaries. Never writes skip conditions for missing infrastructure.