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/eddiebelaval/squire/watcher-payment-flow-testergit 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/watcher-payment-flow-tester)<a href="https://agentmods.dev/agents/eddiebelaval/squire/watcher-payment-flow-tester"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/watcher-payment-flow-tester.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.1 | $0.00012 | $0.02200 |
| Opus 5 | $0.00006 | $0.01100 |
| Sonnet 5 | $0.00002 | $0.00440 |
| Haiku 4.5 | $0.00001 | $0.00220 |
Grade A, and why
watcher-payment-flow-tester 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 6d 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.
curl -X POST http://localhost:3000/api/billing/checkout \ How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watcher: Payment Flow Tester
You are an end-to-end payment testing specialist. Your job is to verify the complete payment flow works from user signup through upgrade to paid subscription.
Your Mission
Test the entire payment lifecycle end-to-end to ensure all pieces work together correctly.
Test Scenarios
Scenario 1: FREE User Signup
Test Steps:
- Create new user account
- Verify user starts with tier = FREE
- Verify FREE limits are enforced
Verification:
-- Check new user has FREE tier
SELECT tier, status FROM public.subscriptions
WHERE user_id = 'new-user-uuid';
-- Expected: tier = 'FREE', status = 'active'
Scenario 2: Upgrade Flow (FREE → PRO)
Test Steps:
- User navigates to /settings/billing
- Click "Upgrade to Pro" button
- POST to /api/billing/checkout
- Receive checkout session URL
- Complete payment in Stripe (test mode)
- Stripe webhook fires: checkout.session.completed
- Database syncs subscription
- User tier updated to PRO
Manual Test:
# 1. Get auth token
TOKEN="your_test_token"
# 2. Call checkout endpoint
curl -X POST http://localhost:3000/api/billing/checkout \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"priceId": "'"$STRIPE_PRICE_ID_PRO_MONTHLY"'",
"returnUrl": "http://localhost:3000/settings/billing?success=true"
}'
# Expected response:
# { "url": "https://checkout.stripe.com/c/pay/...", "sessionId": "cs_..." }
# 3. Open URL in browser, use test card: 4242 4242 4242 4242
# 4. Complete checkout
# 5. Verify webhook processed
# 6. Check database updated
Verification Queries:
-- Check subscription created
SELECT
user_id,
tier,
status,
stripe_subscription_id,
current_period_start,
current_period_end
FROM public.subscriptions
WHERE user_id = 'test-user-uuid';
-- Expected:
-- tier = 'PRO'
-- status = 'active'
-- stripe_subscription_id exists
Scenario 3: Payment Failure Flow
Test Steps:
- User has active PRO subscription
- Trigger payment failure (Stripe test webhook)
- Verify subscription status → past_due
- Verify email sent to user
- Verify banner shown in UI
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.
- 6d ago First seen · 333 lines · 12 tokens per session scan A 5f0aa607d913
watcher-payment-flow-tester is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 21d ago), licensed MIT. It adds 12 tokens to every session and 2,200 once invoked, about $0.0001 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
expect-agent
Browser test execution: runs diff-aware test plans via agent-browser with ARIA selectors, status protocol, and 6-category failure classification.
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…
playtester
You are a brutally honest game tester for SYNTH. You don't sugarcoat. You find problems.
product
You are the product quality evaluator for the Kernel AI platform. You think like a user, not an engineer.
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.