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-8-tmcgit 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-8-tmc)<a href="https://agentmods.dev/agents/telivityai/otaip/stage-8-tmc"><img src="https://agentmods.dev/badge/agents/telivityai/otaip/stage-8-tmc.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 | $0.00000 | $0.01050 |
| Opus 5 | $0.00000 | $0.00525 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
stage-8-tmc 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 8 -- TMC (Travel Management Company) Agents
Package: @otaip/agents-tmc
Traveler profile management, corporate account policies, mid-office automation, reporting/analytics, and duty of care.
Agent 8.1 -- Traveler Profile
ID: 8.1
Class: TravelerProfile
Status: Implemented
Traveler preferences, identity documents, loyalty programs, and PNR prefill. CRUD operations plus apply-to-PNR for generating SSR/APIS commands.
Input:
operation--'get' | 'create' | 'update' | 'apply_to_pnr' | 'search'- Profile data: name, DOB, nationality, passport, loyalty numbers, seat/meal preference, contact info, corporate/employee ID, department, cost center
- PNR application: GDS system, segments for APIS generation
Output:
profile?-- traveler profile recordprofiles?-- search results- PNR application: generated SSR/OSI commands
Agent 8.2 -- Corporate Account
ID: 8.2
Class: CorporateAccount
Status: Implemented
Corporate travel policy management, negotiated fare lookup, and booking validation against policy rules (cabin limits, fare ceilings, advance booking, preferred/blacklisted airlines).
Input:
operation--'get_account' | 'create_account' | 'update_account' | 'validate_booking' | 'get_policy' | 'list_accounts' | 'get_preferred_suppliers'- Account data: company name, IATA number, travel policy, negotiated fares, contact info
- Booking validation: segments, cabin, fare amount, advance days
Output:
account?-- corporate account recordaccounts?-- account listvalidation?-- policy violations (hard/soft) with detailspolicy?-- travel policy rulessuppliers?-- preferred suppliers
Agent 8.3 -- Mid-Office Automation
ID: 8.3
Class: MidOfficeAutomation
Status: Implemented
PNR quality checks and ticketing deadline monitoring. Scans PNRs for 10 issue types: TTL urgent/approaching, missing segment status, missing APIS, missing contact/FOP, duplicate PNR, passive segment, policy violation, married segment incomplete.
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.
- 5d ago First seen · 110 lines · 0 tokens per session scan A a94552fb5788
stage-8-tmc is an agent published in the GitHub repository TelivityAI/otaip (41 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,050 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
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.
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.
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…