Borrowing it
Nothing to install: this file belongs to quangdang46/livekit_agent_simulator. 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/quangdang46/livekit_agent_simulator/main/AGENTS.mdgit clone --depth 1 https://github.com/quangdang46/livekit_agent_simulatorWrote 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/quangdang46/livekit_agent_simulator/agents-md)<a href="https://agentmods.dev/instructions/quangdang46/livekit_agent_simulator/agents-md"><img src="https://agentmods.dev/badge/instructions/quangdang46/livekit_agent_simulator/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.
<a href="https://agentmods.dev/instructions/quangdang46/livekit_agent_simulator/agents-md"><img src="https://agentmods.dev/badge/instructions/quangdang46/livekit_agent_simulator/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.04436 | $0.04436 |
| Opus 5.5 | $0.01774 | $0.01774 |
| Sonnet 5.5 | $0.00887 | $0.00887 |
| Haiku 4.5 | $0.00444 | $0.00444 |
Grade C, and why
livekit_agent_simulator AGENTS.md scanned grade C with 1 finding 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 1mo 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- bv-agent-instructions-v4 --> How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — livekit-agent-simulator
Standalone Python package: MCP + lks CLI. Dials any LiveKit voice agent using
.agent-sim/ in a target repo (config, scenarios, reports). The agent under test is a
black box — we never import or edit target application code unless the user asks.
Boundary
| In scope | Out of scope |
|---|---|
src/livekit_agent_simulator/ |
Target agent source, consumer app code, DB, env |
| Scenario JSONL, Script timing, observer, reports | Parsing project-specific dispatch keys in core |
| LiveKit room + dispatch + sim caller | Agent model stack, tools, business rules |
Opaque dispatch: config.yaml → livekit.dispatch_metadata and scenario Dispatch.metadata
are passed through as JSON strings. Core Python must not interpret consumer-specific keys.
Target repo = path passed as project_root / --root. Consumer wiring examples live in
docs/portability.md — load that file only when the task is target .agent-sim/ setup, not
for package bugs or features.
Product rule: generic core, not fit-to-one-repo
This package ships tools + core capabilities that every LiveKit agent repo can use. It is not a glue layer for one consumer (worker, dashboard, language, brand).
| Do | Do not |
|---|---|
| Build features every target can enable via config / scenario / plugins | Hardcode language, timezone, agent IDs, data topics, or business strings in src/ |
Give extension points (opaque dispatch, observe.*, Script, verify plugins) so users customize |
Parse or special-case consumer keys in core Python |
Put project-specific wiring only in that target’s .agent-sim/ |
Change package defaults to match the last repo we smoked |
Prefer one clear API (record_audio, not aliases) |
Keep “legacy” flags, dual names, or compatibility shims “just in case” |
Customization belongs to the user. We ship knobs and contracts; the target fills
config.yaml, scenarios, plugins. If something only works for one monorepo, it is
wrong for core — fix the design or keep it out of src/.
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.
- 1mo ago Changed · +87 lines · +1,205 tokens per session 997528326173
- 1mo ago Changed · +62 lines · +835 tokens per session scan A → C bc99f2762b43
- 2mo ago First seen · 197 lines · 2,396 tokens per session scan A 90382499381a
livekit_agent_simulator AGENTS.md is an instructions file published in the GitHub repository quangdang46/livekit_agent_simulator (7 stars, last pushed 29d ago), licensed MIT. It adds 4,436 tokens to every session, about $0.0177 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.