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 skills add seatlayer/seatlayer-ai-toolkit --skill integrate-seatlayergit clone --depth 1 https://github.com/seatlayer/seatlayer-ai-toolkitWrote 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/skills/seatlayer/seatlayer-ai-toolkit/integrate-seatlayer)<a href="https://agentmods.dev/skills/seatlayer/seatlayer-ai-toolkit/integrate-seatlayer"><img src="https://agentmods.dev/badge/skills/seatlayer/seatlayer-ai-toolkit/integrate-seatlayer.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.00098 | $0.01504 |
| Opus 5 | $0.00049 | $0.00752 |
| Sonnet 5 | $0.00020 | $0.00301 |
| Haiku 4.5 | $0.00010 | $0.00150 |
Grade A, and why
integrate-seatlayer 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 7d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate SeatLayer
Use the live SeatLayer Markdown documentation as the product source of truth. Adapt SeatLayer to the repository; do not generate a parallel demo application unless the user explicitly asks for one.
Start with repository discovery
-
Read repository agent instructions and contribution guidance.
-
Inspect the package manager, framework, routing, server/client boundary, authentication, tenant model, order/payment flow, environment validation, HTTP conventions, tests, analytics adapter, and deployment platform.
-
Determine whether SeatLayer managed ticketing or the host platform owns payment, commercial orders, tickets, refunds, and fulfilment.
-
Run the read-only doctor when Node.js is available:
node <skill-root>/scripts/doctor.mjs <repository-root> -
State the chosen commerce profile, SeatLayer surface, and discovered host locations before editing.
-
Ask only for business decisions that cannot be discovered safely.
Read references/integration-map.md to select the surface and documentation routes. Read references/safety-contract.md before changing checkout, credential, booking, inventory, or webhook code.
Load focused live documentation
Always begin with:
https://docs.seatlayer.io/llms.txt- the task-specific Markdown routes selected from
integration-map.md
Prefer /<page>/index.md routes. Use
https://docs.seatlayer.io/llms-full.txt only when the task genuinely spans
several product surfaces. Do not invent SDK methods, fields, endpoints, error
codes, or release status from memory.
If live documentation conflicts with this skill, follow the live documentation and report the discrepancy.
Choose the smallest complete integration
Choose the commerce profile first:
- Managed ticketing when SeatLayer owns hosted checkout, Orders, tickets, delivery, refunds, and Door. Use a Hosted Event Page, managed embed, or Organizer Website. Do not add a host booking endpoint.
- Platform/custom commerce when the host owns payment, orders, tickets,
refunds, and fulfilment. Use
SeatPickerfor checkout handoff orSeatingChartfor headless selection, then book from a trusted server. - Private or partner distribution when access is limited by allocation. Choose a hosted access link or an origin-bound buyer access session based on the live channel contract; private means no public link, not disabled inventory.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 165 lines · 98 tokens per session scan A 69d65f543ae0
integrate-seatlayer is a skill published in the GitHub repository seatlayer/seatlayer-ai-toolkit (2 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 1,504 once invoked, about $0.0005 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 skills, from other repositories
memstack-content-product-description
Use this skill when the user says 'product description', 'product listing', 'product copy', 'Amazon listing', 'Shopify listing', 'e-commerce copy', or needs conversion-optimized product descriptions with benefit-driven headlines and platform-specific SEO. Do NOT use for pricing strategy or sales funnels.
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.
klaviyo
Klaviyo email/SMS marketing - profiles, events, flows, segmentation.
web-payments
Stripe Checkout, subscriptions, webhooks, customer portal.
woocommerce
WooCommerce REST API - products, orders, customers, webhooks.
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…