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/synth-laboratories/synth-ai/agents-mdgit clone --depth 1 https://github.com/synth-laboratories/synth-aiWrote 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/synth-laboratories/synth-ai/agents-md)<a href="https://agentmods.dev/instructions/synth-laboratories/synth-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/synth-laboratories/synth-ai/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.01558 | $0.01558 |
| Opus 5 | $0.00779 | $0.00779 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
synth-ai 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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Notes
- PlanetScale now supports PostgreSQL. Treat PlanetScale as Postgres for schema, SQL, and migrations.
CRITICAL: Prod launch checklist
Any synth-ai PyPI release tied to a launch must clear the Packages and SDK
sections of ../synth-dev/launch_checklist.md —
fresh-venv install smoke, typed error imports, backend parity (version-contract),
no unreleased local changes claimed in launch copy. Record published version +
smoke output as proof.
CRITICAL: Managed Research SDK ownership
synth-ai is the canonical home for Managed Research SDK/client, MCP server,
models, transport, schemas, and public SynthClient().research interfaces.
The standalone managed-research package is a compatibility shim only during
the retirement window.
- Keep backend as the contract authority; do not invent SDK behavior that bypasses backend routes, hosted MCP, or the control-plane facade.
- Preserve legacy import and CLI compatibility through shim modules when moving
public surfaces into
synth-ai. - Customer-facing examples should prefer
from synth_ai import SynthClient.
Coding Style
Follow the Synth Style guide: specifications/tanha/references/synthstyle.md (sibling repo).
- Docstrings link to specs. Use
/// See: specifications/tanha/...(Rust) or# See: specifications/tanha/...(Python) on non-trivial public functions/modules. - All errors handled. Rust:
thiserror, neverunwrap(). Python: never swallow exceptions. - Naming. No abbreviations. Units last:
timeout_ms,retry_count_max. - Comments say why. Code says what. Comments say why. Specs say the full story.
CRITICAL: Running The Backend Locally
Do not hand-roll the local stack. Use the synth-dev repo (sibling checkout under ~/Documents/GitHub/).
cd ../synth-dev
./scripts/local.sh up slot1
See ../synth-dev/README.md for prerequisites (Colima, uv, secrets), fixed slot port maps, and commands (local.sh status, doctor, down, etc.).
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.
- 4d ago First seen · 126 lines · 1,558 tokens per session scan A 5f3c4e6f9fa6
synth-ai AGENTS.md is an instructions file published in the GitHub repository synth-laboratories/synth-ai (82 stars, last pushed 13d ago), licensed MIT. It adds 1,558 tokens to every session, about $0.0078 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-autoresearch AGENTS.md
Instructions for TheGreenCedar/codex-autoresearch, covering agents.md, purpose and scope, canonical sources, stable product boundaries and source and package boundaries.
llm-wiki AGENTS.md
Instructions for BogdanovychA/llm-wiki, covering інструкції для агентів: хранитель llm wiki, 1. структура каталогів, 2. загальні конвенції, 3. шаблони сторінок та стандарти форматування and назви файлів.
Polaris AGENTS.md
AGENTS.md instructions for sponge-b0b/Polaris, covering agents.md, purpose and authority, domain vocabulary, coding conduct and secrets.
arandu CLAUDE.md
Instructions for vdittgen/arandu, covering arandu, architecture, top-level packages, commands and coding standards.
nbp-skillforge AGENTS.md
Instructions for nbpadilha/nbp-skillforge, covering agents.md, what this is, the one rule that matters, before you finish a change and conventions.
openlegion CLAUDE.md
Claude Code instructions for openlegion-ai/openlegion, covering claude.md — engine, commands & testing, git workflow, work patterns and architecture.