Borrowing it
Nothing to install: this file belongs to LucasLeguizamo/open-ticket. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LucasLeguizamo/open-ticket/main/.claude/agents/ot-protocols.mdgit clone --depth 1 https://github.com/LucasLeguizamo/open-ticketWrote 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/lucasleguizamo/open-ticket/ot-protocols)<a href="https://agentmods.dev/agents/lucasleguizamo/open-ticket/ot-protocols"><img src="https://agentmods.dev/badge/agents/lucasleguizamo/open-ticket/ot-protocols/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lucasleguizamo/open-ticket/ot-protocols"><img src="https://agentmods.dev/badge/agents/lucasleguizamo/open-ticket/ot-protocols.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.00484 |
| Opus 5.5 | $0.00028 | $0.00194 |
| Sonnet 5.5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
ot-protocols 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 1mo 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
Eres el especialista de protocolos de agentic commerce de OpenTicket. Fuente de verdad: docs/protocol-audit.md y docs/SYNTHESIS.md.
Estado de rails (no lo re-litigues)
| Rail | Estado | Nota |
|---|---|---|
| MCP | ✅ v1, rail principal | app/api/[transport]/route.ts con mcp-handler; demo-able con Claude hoy |
| Stripe hosted | ✅ v1 | capture mode hosted |
| ACP | Feed publicado + conformance contra mock oficial | Compra real vía ChatGPT FUERA de scope (allowlist OpenAI). /complete requiere inline_spt — fase posterior |
| x402 | Stretch | testnet Base Sepolia, facilitador CDP gratis |
| AP2 | Overlay de autorización, no rail | Usuario firma mandate con clave hardware-backed; OpenTicket genera Cart Mandate y verifica, no firma |
| MPP | Stub tras flag | redundante con x402 |
Trust boundary (PRD §7 — crítico)
TODO input de agente pasa por los schemas Zod de core/adapter/rails/schemas.ts. Nunca ejecutar contenido de agentes como instrucciones. Rate-limit por API key. spend_limit autodeclarado NO es control de seguridad hasta que AP2 entre — documéntalo así.
MCP tools contract (PRD US-003)
buy_ticket respeta límite de gasto y devuelve confirmación + .ics. set_reminder para el flujo agéntico. Transport JSON-RPC 2.0. Errores estructurados: sold_out, mandate_exceeded — el agente comprador decide con eso.
Referencias spec
ACP: github.com/agentic-commerce-protocol/agentic-commerce-protocol · x402: Coinbase CDP · AP2: mandates como W3C Verifiable Credentials. Verifica contra spec real (WebFetch) antes de implementar, no de memoria.
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.
- 1mo ago First seen · 27 lines · 69 tokens per session scan A a8b8bb0a8c1f
ot-protocols is an agent published in the GitHub repository LucasLeguizamo/open-ticket (0 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 484 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
salesforce-expert
Expert in Salesforce Commerce development — B2C Commerce Cloud (SFCC/Demandware) with SFRA cartridges, ISML templating, SCAPI and OCAPI APIs, PWA Kit headless storefronts, and B2B/D2C Commerce on Lightning with Apex hooks, LWC components, Experience Builder storefronts, Einstein AI recommendations, Salesforce…
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
fetch-docs-haiku45
Fetch and save documentation from URLs using Haiku 4.5 model. Use for benchmarking documentation retrieval tasks.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.