Borrowing it
Nothing to install: this file belongs to aidyou/chatspeed. 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/aidyou/chatspeed/main/AGENTS.mdgit clone --depth 1 https://github.com/aidyou/chatspeedWrote 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/aidyou/chatspeed/agents-md)<a href="https://agentmods.dev/instructions/aidyou/chatspeed/agents-md"><img src="https://agentmods.dev/badge/instructions/aidyou/chatspeed/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/aidyou/chatspeed/agents-md"><img src="https://agentmods.dev/badge/instructions/aidyou/chatspeed/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.01310 | $0.01310 |
| Opus 5.5 | $0.00524 | $0.00524 |
| Sonnet 5.5 | $0.00262 | $0.00262 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
chatspeed 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 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.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChatSpeed Root Rules
This file is for global rules only. Keep it short. When a subdirectory has its own AGENTS.md or CONSTITUTION.md, follow the more specific file there.
Personal Preferences
- Prefer small, targeted changes. Do not do unrelated cleanup or refactors.
- Reuse existing patterns before adding abstractions.
- Do not stage, commit, branch, or rewrite git history unless explicitly asked.
- Git commit messages must be in English.
- Unless the user explicitly requests it, do not proactively commit the
chatspeed-docsorwebsitesubmodules. - Unless explicitly requested otherwise, reply in the same language as the user's message.
- Final reports should be concise and include what changed, what was verified, and any remaining risk.
Project Shape
- ChatSpeed is a Tauri 2 desktop application: the Rust backend and Tauri commands live under
src-tauri/, while the Vue 3 + Vite frontend lives undersrc/. - Frontend conventions are Vue 3 Composition API with
<script setup>, Element Plus, Pinia, Vue Router, vue-i18n, and SCSS. Reuse these choices instead of introducing parallel UI or state-management stacks. - Use pnpm for frontend dependencies and scripts;
package.jsonandpnpm-lock.yamlare authoritative. Use Cargo fromsrc-tauri/for Rust dependencies and commands. Do not use npm or yarn, and do not create another lockfile. - Keep cross-boundary changes explicit: trace Vue/TypeScript or JavaScript calls through the Tauri command/event contract to Rust, and verify both sides when that contract changes.
General Workflow
- Read relevant files before editing.
- Ask before broad refactors, dependency additions, schema migrations, destructive actions, or behavior changes outside the request.
- Work a change through plan, confirm (when it is significant), execute, verify, correct, and report.
- Never delete an existing test case unless the code it covers was explicitly removed; adapt tests when an API or the logic underneath them changes.
- For small localized fixes, proceed directly.
- Prefer the narrowest useful verification. If you cannot run verification, say so.
- When editing or adding files or modules, test only the affected page, module, or focused behavior. Do not run whole-repository tests unless the user explicitly asks, because they are prone to timing out.
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 · +5 lines · +141 tokens per session 244b6e1f82f7
- 1mo ago First seen · 58 lines · 1,169 tokens per session scan A 231ae98d7518
chatspeed AGENTS.md is an instructions file published in the GitHub repository aidyou/chatspeed (21 stars, last pushed yesterday), licensed MIT. It adds 1,310 tokens to every session, about $0.0052 per session on Opus 5.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).
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.