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 skills/trayio/tray-plugins/tray-patternsnpx skills add trayio/tray-plugins --skill tray-patternsgit 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.00078 | $0.02075 |
| Opus 5 | $0.00039 | $0.01038 |
| Sonnet 5 | $0.00016 | $0.00415 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade A, and why
tray-patterns 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 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.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tray Workflow Patterns
Consult this when building workflows or debugging structure issues.
Incremental Build Flow
Workflows are built step-by-step, not as monolithic JSON:
create_workflow(project_id, workflow_name, trigger={...})
→ workflow_id + version_id
add_workflow_steps(workflow_id, version_id, steps=[{...}, {...}, ...])
→ new version_id
update_workflow_steps(workflow_id, new_version_id, steps=[{step_name, properties, ...}, ...])
→ newer version_id
CRITICAL: Version ID chaining — Every mutating tool returns a version_id. You MUST pass it to the next call. Stale version_ids cause API errors (which include the latest version_id for recovery).
Trigger Properties
For the canonical trigger connector table (names, versions, which triggers need public_url), see tray-connectors. The one trigger whose structure is worth codifying here is the scheduled daily operation — it has the richest required-field shape.
Scheduled trigger — daily operation
{
"public_url": {"type": "jsonpath", "value": "$.env.public_url"},
"hour": {"type": "string", "value": "9"},
"minute": {"type": "string", "value": "0"},
"tz": {"type": "string", "value": "Europe/London"},
"day_of_week": {
"type": "object",
"value": {
"monday": {"type": "boolean", "value": true},
"tuesday": {"type": "boolean", "value": true},
"wednesday": {"type": "boolean", "value": true},
"thursday": {"type": "boolean", "value": true},
"friday": {"type": "boolean", "value": true},
"saturday": {"type": "boolean", "value": true},
"sunday": {"type": "boolean", "value": true}
}
}
}
day_of_week must be explicit — always set all 7 days. Do not rely on defaults.
Trigger output uses zero-indexed month and day_of_week — January is 0, December is 11; Monday is 0, Sunday is 6. Branches that compare the trigger's day/month output against a literal day name will silently route wrong on production runs (the validator can't catch it because the jsonpaths are valid). For any date arithmetic prefer the Date Time Helper's Get Date Property operation over parsing the trigger payload directly.
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 · 149 lines · 78 tokens per session scan A 3f49848b3341
tray-patterns is a skill published in the GitHub repository trayio/tray-plugins (9 stars, last pushed 14d ago), licensed Apache-2.0. It adds 78 tokens to every session and 2,075 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…