What is symphony-ts AGENTS.md?

Repository instructions for a TypeScript monorepo, meaning one repository that contains shared code, tests, and example applications. They describe its folders, commands, style, and testing approach.

Use them when adding or changing library code, tests, example apps, documentation assets, or build configuration.

They help coding agents place files correctly and use the project’s required tools, such as pnpm, Node.js, TypeScript, and Vitest.

How OasAIStudio/symphony-ts configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to OasAIStudio/symphony-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/OasAIStudio/symphony-ts/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/OasAIStudio/symphony-ts

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/oasaistudio/symphony-ts/agents-md/github.svg)](https://agentmods.dev/instructions/oasaistudio/symphony-ts/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/oasaistudio/symphony-ts/agents-md"><img src="https://agentmods.dev/badge/instructions/oasaistudio/symphony-ts/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/oasaistudio/symphony-ts/agents-md"><img src="https://agentmods.dev/badge/instructions/oasaistudio/symphony-ts/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 899 This file is loaded in full into every session.

When invoked 899 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00899	$0.00899
Opus 5.5	$0.00360	$0.00360
Sonnet 5.5	$0.00180	$0.00180
Haiku 4.5	$0.00090	$0.00090

Measured 2mo ago against content hash 8fa3dd4dc6ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

symphony-ts 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 2mo 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.

AGENTS.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

This is a TypeScript monorepo with a full implementation. Key top-level paths:

src/: library source code (TypeScript, ESM)
tests/: Vitest test suite mirroring src/ structure
apps/: example/demo applications (e.g. apps/todo-linear-demo/)
dist/: compiled output (generated by pnpm build, not committed)
docs/: supplementary documentation
biome.json: Biome lint and format configuration
tsconfig.json / tsconfig.build.json: TypeScript project configs
vitest.config.ts: test runner configuration
README.upstream.md / SPEC.upstream.md: upstream reference docs

Keep new source files under src/, tests under tests/, and additional apps under apps/<name>/. Store design assets and media under docs/assets/ or .github/media/.

Build, Test, and Development Commands

The package manager is pnpm (>=10.0.0) and the runtime target is Node.js >=22.

Command	Purpose
`pnpm install`	Install dependencies
`pnpm build`	Compile TypeScript to `dist/` via `tsc`
`pnpm test`	Run all tests once with Vitest
`pnpm test:watch`	Run tests in watch mode
`pnpm typecheck`	Type-check without emitting output
`pnpm lint`	Lint and check formatting with Biome
`pnpm format`	Auto-format source files with Biome

Coding Style & Naming Conventions

Keep Markdown concise, imperative, and specific to this repository. Use sentence-style prose in docs and short sections with meaningful headings. Name new files clearly by purpose, for example ARCHITECTURE.md, docs/setup.md, or apps/orchestrator/.

Match the formatter and linter of the language you introduce. If you add source code, also add the corresponding config files in the same change.

Testing Guidelines

The repository uses Vitest. All tests live under tests/ and mirror the src/ directory structure. Run pnpm test to execute the full suite. Prefer naming test files after the module they cover (e.g. tests/orchestrator/core.test.ts for src/orchestrator/core.ts) and name individual test cases after observable behavior.

Read the full file on GitHub · 67 lines

Changes

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.

2mo ago First seen · 67 lines · 899 tokens per session scan A 8fa3dd4dc6ac

Subscribe to this mod's changes

symphony-ts AGENTS.md is an instructions file published in the GitHub repository OasAIStudio/symphony-ts (424 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 899 tokens to every session, about $0.0036 per session on Opus 5.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.

symphony-ts AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
symphony-ts AGENTS.mdOasAIStudio/symphony-ts	Instructions file	424	7mo ago	Apache-2.0	A	899	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

symphony-ts: Instructions file for Codex