What is Isartor copilot-instructions.md?

Project instructions for Isartor, including its commands, architecture, and coding conventions. Isartor is a software project built with Rust, a programming language.

Use them to run the project’s build and release commands, full or targeted tests, Rust formatting and lint checks, and performance benchmarks.

They give a coding agent the project-specific information needed to build, test, format, lint, and benchmark the code correctly.

How isartor-ai/Isartor configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to isartor-ai/Isartor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/isartor-ai/Isartor/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/isartor-ai/Isartor

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/isartor-ai/isartor/copilot-instructions/github.svg)](https://agentmods.dev/instructions/isartor-ai/isartor/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/isartor-ai/isartor/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/isartor-ai/isartor/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/isartor-ai/isartor/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/isartor-ai/isartor/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,358 This file is loaded in full into every session.

When invoked 1,358 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01358	$0.01358
Opus 5.5	$0.00543	$0.00543
Sonnet 5.5	$0.00272	$0.00272
Haiku 4.5	$0.00136	$0.00136

Measured 2mo ago against content hash d19d6ebdaeb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Isartor 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 2mo 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.

.github/copilot-instructions.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot Instructions for Isartor

Build, test, and lint commands

Use cargo build for a local build and cargo build --release or make build for a release build.
Run the full test suite with cargo test --all-features or make test.
Run formatting and lint checks the same way CI does:
- cargo fmt --all -- --check
- cargo clippy --all-targets --all-features -- -D warnings
Run a single test by targeting the integration-test binary that owns it, for example:
- cargo test --test scenario_suite deflection_rate_at_least_60_percent -- --nocapture
- cargo test --test integration_suite body_survives_all_middleware -- --nocapture
- cargo test --test unit_suite exact_cache_miss_then_hit -- --nocapture
- cargo test --test integration_test redis_exact_cache_round_trip -- --ignored --nocapture
Run Criterion benches with the explicit bench target, for example:
- cargo bench --bench cache_latency
- cargo bench --bench e2e_pipeline
Run the benchmark harness with:
- make benchmark
- make benchmark-dry-run
- python3 benchmarks/run.py --url http://localhost:8080 --input benchmarks/fixtures/faq_loop.jsonl --requests 500
Development setup in CONTRIBUTING.md expects Rust 1.75+ and notes Docker for integration-test workflows.
Update tests in tests/, targeting the owning integration-test binary (unit_suite, integration_suite, scenario_suite, or integration_test) rather than assuming per-file test targets.
Treat README.md as the public feature list and top-level product entry point.
For any implementation ticket that changes behavior, capabilities, supported providers/tools, CLI/API surfaces, configuration, or UX, update the affected documentation in the same change:
- README.md feature list and user-facing capability callouts
- supplementary docs in docs/
- published docs in docs-site/src/
If the implementation changes system structure, request flow, supported surfaces, deployment model, routing strategy, cache semantics, or other lasting technical trade-offs, also update:
- docs/architecture-decisions.md
- docs-site/src/concepts/architecture-decisions.md
- docs-site/src/concepts/architecture.md
Do not defer these documentation or architecture updates to a follow-up ticket when the implementation itself is shipping now.

Read the full file on GitHub · 64 lines

Changes

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.

2mo ago First seen · 64 lines · 1,358 tokens per session scan A d19d6ebdaeb9

Subscribe to this mod's changes

Isartor copilot-instructions.md is an instructions file published in the GitHub repository isartor-ai/Isartor (21 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,358 tokens to every session, about $0.0054 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.

HuggingFace Languages Rust agentic-ai ai-gateway air-gapped anthropic candle

Isartor copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Isartor copilot-instructions.mdisartor-ai/Isartor	Instructions file	21	5mo ago	Apache-2.0	A	1,358	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

Isartor: Instructions file for GitHub Copilot