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/telivityai/otaip/stage-4-ticketinggit clone --depth 1 https://github.com/TelivityAI/otaipWrote 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/telivityai/otaip/stage-4-ticketing)<a href="https://agentmods.dev/agents/telivityai/otaip/stage-4-ticketing"><img src="https://agentmods.dev/badge/agents/telivityai/otaip/stage-4-ticketing.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.00000 | $0.01127 |
| Opus 5 | $0.00000 | $0.00563 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
stage-4-ticketing 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 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.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 4 -- Ticketing Agents
Package: @otaip/agents-ticketing
Electronic ticket issuance, EMD management, void processing, itinerary delivery, and document verification.
Agent 4.1 -- Ticket Issuance
ID: 4.1
Class: TicketIssuance
Status: Implemented
ETR (Electronic Ticket Record) generation with conjunction ticket support (auto-split for >4 coupons), BSP reporting fields, and commission handling.
Input (TicketIssuanceInput):
record_locator-- 6-char PNRissuing_carrier-- 2-letter IATA codepassenger_name-- LAST/FIRST formatsegments-- flight segments with carrier, flight number, class, fare basis, dates, baggagebase_fare,base_fare_currency-- fare amountequivalent_fare?,equivalent_fare_currency?-- currency conversiontaxes-- tax breakdown itemsfare_calculation-- fare calculation lineform_of_payment-- CASH, CREDIT_CARD, INVOICE, MISCELLANEOUSendorsements?,commission?,bsp_reporting?,original_issue?
Output (TicketIssuanceOutput):
tickets--TicketRecord[](13-digit number, coupons with status, fare/tax breakdown, FOP, commission, BSP fields)total_coupons-- total across all ticketsis_conjunction-- whether conjunction tickets were generated
Agent 4.2 -- EMD Management
ID: 4.2
Class: EmdManagement
Status: Implemented
EMD-A (associated) and EMD-S (standalone) issuance with RFIC/RFISC handling and coupon lifecycle management.
Input (EmdManagementInput):
emd_type--'EMD-A' | 'EMD-S'record_locator,issuing_carrier,passenger_nameservices-- array of services with RFIC code (A-G), RFISC, description, amount, associated ticket/coupon for EMD-Arelated_ticket_number?-- for EMD-A
Output (EmdManagementOutput):
emd--EmdRecord(13-digit EMD number, coupons, amounts)coupon_count
Agent 4.3 -- Void Agent
ID: 4.3
Class: VoidAgent
Status: Implemented
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 · 119 lines · 0 tokens per session scan A 5afd7aa43738
stage-4-ticketing is an agent published in the GitHub repository TelivityAI/otaip (41 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,127 tokens. 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-30.
Other agents, from other repositories
framework-scout
Open-source agent framework assessor that evaluates community health, supersession risk, architecture alignment, and governance sustainability to classify investment readiness before committing resources.
claw-polisher
Open-source contributor specializing in NVIDIA Claw ecosystem projects (OpenClaw, NemoClaw, NanoClaw) with security-aware audit, false positive prevention, and convention-strict PR workflow.
marketing-claw-playbook
This playbook lets an external claw act as FlowWink's marketing department — running paid growth, content, audience research, and reporting end-to-end.
agent_invite
The onboarding text handed to an external agent that will operate a FlowWink instance over MCP — connection, protocols, resources and cadence.
finance-claw-playbook
This playbook lets an external claw act as FlowWink's finance department — running invoicing, expense booking, bank reconciliation, and period close (record-to-report) — without…
operations-claw-playbook
This playbook lets an external claw act as FlowWink's operations department — running inventory, purchasing, order fulfillment, manufacturing, and field service — without FlowPi…