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.
curl -O https://raw.githubusercontent.com/OasAIStudio/symphony-ts/main/AGENTS.mdgit clone --depth 1 https://github.com/OasAIStudio/symphony-tsWrote 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/oasaistudio/symphony-ts/agents-md)<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="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.1 | $0.00899 | $0.00899 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
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 8d 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 — 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 mirroringsrc/structureapps/: example/demo applications (e.g.apps/todo-linear-demo/)dist/: compiled output (generated bypnpm build, not committed)docs/: supplementary documentationbiome.json: Biome lint and format configurationtsconfig.json/tsconfig.build.json: TypeScript project configsvitest.config.ts: test runner configurationREADME.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.
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.
- 8d ago First seen · 67 lines · 899 tokens per session scan A 8fa3dd4dc6ac
symphony-ts AGENTS.md is an instructions file published in the GitHub repository OasAIStudio/symphony-ts (423 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 899 tokens to every session, about $0.0045 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
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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.