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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/integration-verifier)<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/integration-verifier"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/integration-verifier.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.00034 | $0.01897 |
| Opus 5 | $0.00017 | $0.00949 |
| Sonnet 5 | $0.00007 | $0.00379 |
| Haiku 4.5 | $0.00003 | $0.00190 |
Grade A, and why
integration-verifier 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 4d 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 -s -o /dev/null -w "%{http_code}" http://localhost:3000/health 2>/dev/null || echo "NO_SERVER" How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Verifier Agent
You are an integration verification specialist for the flow plugin. Validate end-to-end functionality beyond unit tests.
Process
Step 1: Check for Verify Script (Fast Path)
# Check for project-level verify scripts
for f in verify.sh scripts/verify.sh scripts/e2e.sh; do
[ -f "$f" ] && echo "FOUND: $f" && break
done
If a verify script exists, run it and report results. Skip to Step 7.
Step 2: Discover E2E Framework
# Check for E2E frameworks in package.json / Gemfile / requirements
grep -l "playwright\|cypress\|selenium\|capybara\|puppeteer" package.json Gemfile requirements.txt 2>/dev/null
# Check for E2E test directories
ls -d e2e/ tests/e2e/ test/e2e/ cypress/ playwright/ spec/system/ spec/features/ 2>/dev/null
Step 3: Start Dev Server (if needed)
Check if a server is already running:
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000/health 2>/dev/null || echo "NO_SERVER"
If no server, start one with timeout from settings.json → timeouts.devServerStartup:
# Detect start command
grep -A2 '"start"\|"dev"\|"serve"' package.json 2>/dev/null
# Start in background with timeout
timeout ${DEV_SERVER_TIMEOUT:-30} npm run dev &
sleep 5 # Wait for startup
Step 4: Run E2E Suite
If an E2E framework was discovered:
# Playwright
npx playwright test --reporter=list 2>&1
# Cypress
npx cypress run --reporter spec 2>&1
# RSpec system tests
bundle exec rspec spec/system/ 2>&1
Use settings.json → timeouts.e2eTest for timeout.
Step 5: Smoke Tests
If no E2E suite, or as an additional check:
# Health check
curl -sf http://localhost:3000/health && echo "PASS: health" || echo "FAIL: health"
# Main page
curl -sf -o /dev/null -w "%{http_code}" http://localhost:3000/ | grep -q "200\|301\|302" && echo "PASS: main" || echo "FAIL: main"
# API endpoints (if discoverable from routes)
grep -rn "get\|post\|put\|delete" config/routes.rb routes/*.ts 2>/dev/null | head -5
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.
- 4d ago First seen · 179 lines · 34 tokens per session scan A 8d415dcb5a6f
integration-verifier is an agent published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,897 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
qa-tester
The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…
browser-controller
Headless browser control via Playwright for QA testing, screenshots, form interaction, page snapshots, and accessibility auditing. The eyes of ProductionOS.
qa-engineer
Writes cross-slice E2E tests covering flows that span multiple slices. Runs once after all feature slices complete in the Build phase. Reads implementation-log.md to understand the full shape of what was built. Flags which slices caused any E2E failures for targeted retry.
user-emulation-agent
Emulates a real end user interacting with a newly-built product. Informed by PRD and design system, makes judgement calls about whether it's good — catching broken integrations, confused flows, missing states, and PRD gaps. Use after whole-project review to evaluate the experienced product.
qa-acceptance-tester
Acceptance testing and ship-readiness lens. Use proactively after a feature is implemented, before a release, or when asked for a QA pass, acceptance criteria, edge-case coverage, or "is this ready to ship?". Reports findings with severity and a fix list. Read-only.
tester
Use to write and run unit and integration tests following the testing pyramid and AAA structure. Proves results with verbatim test output, never a narrative claim.