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/chyinan/kokoro-engine/agents-mdgit clone --depth 1 https://github.com/chyinan/Kokoro-EngineWrote 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/chyinan/kokoro-engine/agents-md)<a href="https://agentmods.dev/instructions/chyinan/kokoro-engine/agents-md"><img src="https://agentmods.dev/badge/instructions/chyinan/kokoro-engine/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.00662 | $0.00662 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
Kokoro-Engine 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Kokoro Engine is a Tauri v2 app with a React/TypeScript frontend and Rust backend. Frontend code lives in src/: main.tsx and App.tsx are entry points, src/components/ui holds primitives, src/features holds feature modules, src/lib holds bridge/services/tests, src/ui holds product UI/locales, and src/windows holds extra Tauri windows. Backend code lives in src-tauri/src: IPC is in commands, with domain modules such as llm, tts, stt, vision, mods, mcp, and ai. Assets are in public, pictures, and src/assets; sample mods are in mods; docs are in docs.
Build, Test, and Development Commands
npm install: install JavaScript dependencies.npm run tauri dev: run the full desktop app with Vite.npm run dev: run the Vite frontend only.npm run build: typecheck withtscand build frontend assets.npm run tauri build: build a distributable Tauri app.npm test: run Vitest unit tests.cargo test --manifest-path src-tauri/Cargo.toml: run Rust tests.cargo clippy --manifest-path src-tauri/Cargo.toml --lib -- -D warnings: check Rust warnings before review.
Coding Style & Naming Conventions
Use strict TypeScript, React function components, and @/* imports when they improve clarity. Match existing two-space TypeScript indentation and Rust rustfmt defaults. Name React components and TSX files with PascalCase, hooks as useSomething, utility files in local style such as audio-player.ts, and Rust modules/files with snake_case. Keep user-facing strings in src/ui/locales/*.json.
Testing Guidelines
Vitest tests live beside frontend code as *.test.ts or *.test.tsx. Rust tests are inline #[cfg(test)] modules or files such as src-tauri/src/vision/tests/*.rs. Add focused tests for changed behavior, especially IPC bridges, providers, memory, chat, audio, and vision. Run the targeted suite for your area plus broader checks when risk is shared, for example npm test and cargo test --manifest-path src-tauri/Cargo.toml llm.
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 · 27 lines · 662 tokens per session scan A b3b0e493b66a
Kokoro-Engine AGENTS.md is an instructions file published in the GitHub repository chyinan/Kokoro-Engine (141 stars, last pushed 1mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0033 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
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).