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 commands/eddiebelaval/squire/testgit 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/commands/eddiebelaval/squire/test)<a href="https://agentmods.dev/commands/eddiebelaval/squire/test"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/test.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
test 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 yesterday.
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
/test - Test Feature with Playwright
You are testing a feature using Playwright MCP to verify it works.
-
Ensure Comet is Ready
- Run
~/mcp-comet-bridge/check-and-launch.shto ensure Comet browser is running with debugging - This happens automatically - no user action needed
- Run
-
Ask About the Feature
- What URL to test?
- What should work?
- Any specific user flows?
- Mobile or desktop (or both)?
-
Open Browser
- Navigate to the URL
- Take initial screenshot
-
Test User Flow
- Perform the actions user described
- Check for visual issues
- Verify interactive elements work
- Test keyboard navigation (accessibility)
- Take screenshots at key steps
-
Check for Problems
- Console errors?
- Network failures?
- Visual bugs?
- Broken functionality?
-
Mobile Testing (if applicable)
- Resize to mobile dimensions
- Test touch interactions
- Check responsive design
-
Report Findings Format:
✅ What Works:
- [List working features]
❌ Issues Found:
- [List problems with screenshots]
💡 Suggestions:
- [Improvements noticed]
Screenshots:
- [Attach relevant screenshots]
-
Fix Issues (if any found)
- Address each problem
- Re-test to verify fix
- Continue until everything works
Important:
- Use Playwright MCP browser tools, don't ask user to check manually
- Be thorough - check edge cases
- Provide visual proof with screenshots
- Fix issues immediately, don't just report them
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.
- yesterday First seen · 62 lines · 0 tokens per session scan A 54c9adf6870b
test is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 tokens. 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-09-03.
Other commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
visual-verify
Use Playwright MCP to visually verify the UI that was just built or modified.
e2e
Generate and run E2E tests with Playwright.
ux-audit
Walk a live web app AS a real user — interaction-first methodology. Hard gates (console / network / layout-collapse), Persona Lock, Interaction Manifest enforcement, multi-pane stress, visual polish, perfection checklist, 11 scenarios (judgement-density-ordered), Top 5 + self-critique pass + smallest-possible-patch +…