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/yyyzl/push-2-talk/agents-mdgit clone --depth 1 https://github.com/yyyzl/push-2-talkWrote 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/yyyzl/push-2-talk/agents-md)<a href="https://agentmods.dev/instructions/yyyzl/push-2-talk/agents-md"><img src="https://agentmods.dev/badge/instructions/yyyzl/push-2-talk/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.02448 | $0.02448 |
| Opus 5 | $0.01224 | $0.01224 |
| Sonnet 5 | $0.00490 | $0.00490 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade A, and why
push-2-talk 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/holds the React + TypeScript UI (main window, overlay, and notification windows).index.html,overlay.html, andnotification.htmlare the Vite entry points for the three windows.src-tauri/contains the Rust backend,src-tauri/tauri.conf.json, and app icons insrc-tauri/icons/.ui/is for auxiliary UI assets or prototypes used by the frontend.scripts/has build/release helpers;dist/is generated frontend output.tests/contains TypeScript runtime regression tests (tsx --test).
Key Backend Modules (src-tauri/src/)
asr/- Multi-provider ASR with HTTP and realtime modes (Qwen, Doubao, Doubao IME, SenseVoice)pipeline/- Processing pipelines for dictation and assistant modestnl/- Technical Normalization Layer between ASR and LLM (pinyin/phonetic matching, letter merge, hyphen rewrite)learning/- Auto vocabulary learning (coordinator, diff_analyzer, llm_judge, validator, store)builtin_dictionary_updater.rs- Remote builtin hotwords fetch + atomic cache persistence + runtime refresh eventsuia_text_reader.rs- Windows UI Automation text captureopenai_client.rs- Shared LLM client with connection testingconfig.rs- Configuration management with automatic migration
Key Frontend Structure (src/)
pages/- Page components (Dashboard, ASR, Models, LLM, Assistant, Hotkeys, Dictionary, Preferences, History, Help)components/- Reusable UI components (common/, layout/, learning/, live/, modals/, history/, notice/)windows/- Overlay and notification window componentshooks/- Custom React hooks (useAppServiceController, useDictionary, useHotkeyRecording, useUpdater, useTauriEventListeners)types/- TypeScript type definitionsutils/- Utility functions (dictionaryUtils)
Build, Test, and Development Commands
npm installinstalls frontend dependencies.npm run devstarts the Vite dev server for the UI.npm run buildtype-checks and builds the frontend bundle.npm run previewserves the built UI locally.npm run test:tsruns TypeScript runtime tests intests/*.test.ts.npm run tauri devruns the desktop app in dev mode; run as Administrator so global hotkeys work.npm run tauri buildbuilds the NSIS installer only; output insrc-tauri/target/release/bundle/.cd src-taurithencargo build,cargo check, orcargo testfor the Rust backend.cd src-taurithencargo run --bin test_apito manually verify ASR API 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.
- 4d ago First seen · 153 lines · 2,448 tokens per session scan A d822486c7360
push-2-talk AGENTS.md is an instructions file published in the GitHub repository yyyzl/push-2-talk (183 stars, last pushed 3mo ago), licensed MIT. It adds 2,448 tokens to every session, about $0.0122 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.