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/seatlayer/seatlayer-ai-toolkit/verifygit clone --depth 1 https://github.com/seatlayer/seatlayer-ai-toolkitWhat 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.00015 | $0.00270 |
| Opus 5 | $0.00008 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
verify 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 2d 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
Verify SeatLayer
Use the integrate-seatlayer skill and read its verification reference.
- Run the toolkit doctor in strict mode.
- Run the repository's typecheck, unit tests, lint, production build, and existing integration/browser tests.
- Inspect the browser build for server credentials and server-only modules.
- Identify the selected commerce profile. For managed checkout, trace hosted select → payment → Order → ticket → branded return. For custom commerce, trace select → hold → server inspect → trusted order/payment → book.
- Verify only the relevant matrix, including hosted direct/embed/Website routing or private wrong-origin/expired/revoked access where applicable.
- Inspect storage, URLs, logs, analytics, and buyer bundles for secrets, server SDKs, buyer access tokens, and hosted capability URLs.
Use test mode for live probes. Do not create production bookings, cancel live orders, publish charts, or reveal credentials.
Return a pass/fail matrix, commands and results, skipped checks, blockers, and manual steps still required.
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.
- 2d ago First seen · 28 lines · 15 tokens per session scan A 9c3b31f90461
verify is a command published in the GitHub repository seatlayer/seatlayer-ai-toolkit (2 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 270 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-31.
Other commands, from other repositories
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
debug-playwright
Use this command to debug failing Playwright tests in a source-first, evidence-first workflow.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
fd-verify
Verify the implementation — run tests, check regression on affect.md files, review and scan; blocks /fd-done on failure.