Borrowing it
Nothing to install: this file belongs to utensils/claudette. 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/utensils/claudette/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/utensils/claudetteWrote 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/utensils/claudette/copilot-instructions)<a href="https://agentmods.dev/instructions/utensils/claudette/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/utensils/claudette/copilot-instructions/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/utensils/claudette/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/utensils/claudette/copilot-instructions.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.01119 | $0.01119 |
| Opus 5.5 | $0.00448 | $0.00448 |
| Sonnet 5.5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
claudette copilot-instructions.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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudette Repository Instructions
Claudette is a cross-platform desktop orchestrator for parallel Claude Code agents. It uses a Tauri 2 Rust backend, a React/TypeScript frontend, SQLite via rusqlite, Tokio process management, git worktrees, xterm.js terminals, Lua plugins, and a local CLI that talks to the running GUI over IPC.
Follow the existing architecture. Core behavior belongs in the claudette crate under src/. src-tauri/src/commands/ should stay thin Tauri wrappers. Shared data types belong in src/model/ and must derive Serialize. Frontend state lives in Zustand slices under src/ui/src/stores/slices/, not ad hoc globals.
Treat regressions as the main risk. Before changing behavior, identify the current contract: persisted DB fields, Tauri command payloads, CLI output, plugin manifests, settings keys, localized strings, terminal/session semantics, worktree behavior, and visible UI workflows. Do not remove, rename, or silently reinterpret any of these unless the task explicitly asks for that change.
If a behavior change is intentional, call it out plainly in the PR summary or review response and add/update tests that pin the new behavior. If the change was incidental, preserve compatibility instead.
Do not fix type, lint, or test failures by deleting tests, removing UI controls, dropping state fields, weakening assertions, or broadening types. Fix the underlying mismatch and keep existing user-visible capabilities intact.
Control god files. Do not make already-large files the default destination for new behavior. Prefer a focused module, helper, slice, hook, or component near the owning feature, then wire it through the existing entry point. Be especially cautious with src/diff.rs, src/git.rs, src/plugin.rs, src/mcp.rs, src/mcp_supervisor.rs, the largest siblings of the recently-split src-tauri/src/commands/agent_backends/ directory (gateway_translate.rs, runtime_dispatch.rs, discovery.rs, config.rs), src-tauri/src/commands/*, src-tauri/src/voice.rs, src-tauri/src/ipc.rs, src/ui/src/components/sidebar/Sidebar.tsx, src/ui/src/components/chat/ChatPanel.tsx, src/ui/src/components/chat/ChatInputArea.tsx, src/ui/src/components/terminal/TerminalPanel.tsx, src/ui/src/services/tauri.ts, and large CSS modules.
When touching a god file, keep the diff surgical or extract cohesive behavior first. New code should reduce or isolate complexity, not add another unrelated responsibility.
For subprocess spawns (agent, MCP, setup scripts), use crate::env::enriched_env().apply(&mut cmd) to forward the user's captured shell environment. The capture happens at app launch via prewarm_shell_env in src/env.rs and merges into the env-provider dispatcher at precedence 0 (direnv / mise / dotenv / nix-devshell layer on top). enriched_path() is kept as a backwards-compat accessor returning just PATH — new code should prefer enriched_env() to inherit the full set.
Use the repo's tools. Rust CI expects cargo fmt --all --check, cargo clippy -p claudette -p claudette-server -p claudette-cli --all-targets --all-features with RUSTFLAGS=-Dwarnings, and cargo test --all-features. Frontend CI expects cd src/ui && bun install --frozen-lockfile, bunx tsc --noEmit, bun run lint:css, bun run build, and bun run test.
Always run cd src/ui && bunx tsc -b after TypeScript changes. Vitest uses esbuild and does not type-check the project.
Never edit, rename, or delete released SQL migrations under src/migrations/*.sql. Add a new forward migration and register it in src/migrations/mod.rs.
Use bun, not npm. Keep TypeScript strict and avoid any. Keep Rust cross-platform with explicit #[cfg(...)] gates for OS-specific code.
When spawning subprocesses, never use a raw std::process::Command::new / tokio::process::Command::new. On Windows a GUI process spawns a child with no CREATE_NO_WINDOW flag and a blank cmd.exe window flashes on screen — a bug invisible in dev builds and only seen in release. Use the claudette::process command helper, or CommandWindowExt::no_console_window(). Flag any raw Command::new in review as a Windows console-flash regression unless it is a deliberate user-facing terminal launch using .new_console_window().
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 First seen · 30 lines · 1,119 tokens per session scan A 5340c7d7c6b6
claudette copilot-instructions.md is an instructions file published in the GitHub repository utensils/claudette (83 stars, last pushed 1mo ago), licensed MIT. It adds 1,119 tokens to every session, about $0.0045 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.