Traycer is an open-source application for coordinating multiple AI coding agents while keeping their context and shared memory connected. Developers and teams use it to run agents in parallel, switch models, automate agent discussions, and collaborate on coding work. Catalogue add-ons support workflows around Traycer.
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/traycerai/traycer/agents-mdgit clone --depth 1 https://github.com/traycerai/traycerWrote 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/instructions/traycerai/traycer/agents-md)<a href="https://agentmods.dev/instructions/traycerai/traycer/agents-md"><img src="https://agentmods.dev/badge/instructions/traycerai/traycer/agents-md.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.00806 | $0.00806 |
| Opus 5 | $0.00403 | $0.00403 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
traycer AGENTS.md 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Default branch: main. Bun 1.3.12 workspaces + Nx.
Open-source clients, CLI, and protocol. The Traycer Host and cloud backends
are not here — the CLI provisions a signed host from GitHub Releases; see
docs/DEVELOPMENT.md.
Nested docs (read when editing there)
Map
| Path | Package | Role |
|---|---|---|
protocol/ |
@traycer/protocol |
Client⇄host wire contract |
clients/traycer-cli/ |
@traycer-clients/traycer-cli |
CLI (host install, auth, agents) |
clients/shared/ |
@traycer-clients/shared |
Transport / auth / formatting |
clients/gui-app/ |
@traycer-clients/gui-app |
GUI renderer |
clients/desktop/ |
@traycer-clients/desktop |
Electron shell |
Commands
bun install
bun run build
bun run compile # never tsc directly
bun run lint && bun run format
make test-affected # optional targeted run; CI owns the test gate
bunx nx run @traycer-clients/traycer-cli:build # single package
pre-commit run --all-files # explicit full-repo static validation
make dev-desktop # signed host from Releases + HMR desktop
make dev-desktop VERSION=1.2.3 # pin host release
make dev-desktop talks to the production cloud — no local backends. Details:
docs/DEVELOPMENT.md.
Commits: do not manually run compile / build / lint / format
before committing. pre-commit already runs the affected workspace checks
(build, compile, lint, format). Tests run in CI (test.yml), not in the hook —
only re-run checks yourself when diagnosing a hook or CI failure. Commits need
DCO (git commit -s).
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 · 78 lines · 806 tokens per session scan A 0be7fe55e2ae
traycer AGENTS.md is an instructions file published in the GitHub repository traycerai/traycer (1,383 stars, last pushed today), licensed MIT. It adds 806 tokens to every session, about $0.0040 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-30.
Other instructions, from other repositories
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).
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.
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.