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 instructions/trayio/tray-plugins/agents-mdgit clone --depth 1 https://github.com/trayio/tray-pluginsWhat 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.00831 | $0.00831 |
| Opus 5 | $0.00415 | $0.00415 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade B, and why
tray-plugins AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The `tray` server (configured in `~/.codex/config.toml`) exposes the workflow tools: How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tray Headless for Codex
These instructions let Codex build, modify, run, and debug Tray.ai
workflows in natural language, via the tray MCP server.
Copy this block into the
AGENTS.mdof any project where you want to build Tray workflows (or into~/.codex/AGENTS.mdto make it global). Keep thetray-workflows:begin/endmarkers.
The Tray MCP server
The tray server (configured in ~/.codex/config.toml) exposes the workflow tools:
list_connectors, list_connector_operations, call_connector,
list_authentications, list_service_environments, create_auth_collection,
create_project, create_workflow, add_workflow_steps, update_workflow_steps,
update_workflow_structure, update_workflow_metadata, get_workflow,
validate_workflow, trigger_workflow, get_workflow_execution,
get_workflow_step_detail, and more. Codex namespaces them to the tray server.
If a Tray tool errors with an auth/permission failure, the user likely needs to
sign in: codex mcp login tray. The server acts in the workspace as the signed-in
user — it can create, modify, and delete projects, workflows, and auths, and run
workflows with real side effects. Always confirm before firing a workflow.
How to build (load the skills)
This project ships skills under plugins/codex/tray-workflows/skills/. Load and follow
them — they carry the detailed, load-bearing rules. Do not improvise Tray internals.
build-workflow— the entry point for ALL workflow creation/modification. Load it before anycreate_workflow/add_workflow_steps/update_workflow_stepscall. It defines the mandatory plan → research → build → validate → test flow.research-connector— discover a connector's version, operations, auth, required fields, and DDL values before building a step.tray-connectors— core connector names/versions, the type-wrapper format, step-naming, trigger selection, and jsonpath shapes.tray-patterns— workflow structure: branches, loops (_loopwrapper), callable workflows, scheduled triggers, manual error handling, version_id chaining.tray-gotchas— error debugging and known-weird surfaces.
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 · 60 lines · 831 tokens per session scan B d51a3b405265
tray-plugins AGENTS.md is an instructions file published in the GitHub repository trayio/tray-plugins (9 stars, last pushed 13d ago), licensed Apache-2.0. It adds 831 tokens to every session, about $0.0042 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.