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.
curl -O https://raw.githubusercontent.com/isartor-ai/Isartor/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/isartor-ai/IsartorWrote 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/isartor-ai/isartor/copilot-instructions)<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="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.1 | $0.01358 | $0.01358 |
| Opus 5 | $0.00679 | $0.00679 |
| Sonnet 5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
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 8d 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 — 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 buildfor a local build andcargo build --releaseormake buildfor a release build. - Run the full test suite with
cargo test --all-featuresormake test. - Run formatting and lint checks the same way CI does:
cargo fmt --all -- --checkcargo 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 -- --nocapturecargo test --test integration_suite body_survives_all_middleware -- --nocapturecargo test --test unit_suite exact_cache_miss_then_hit -- --nocapturecargo 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_latencycargo bench --bench e2e_pipeline
- Run the benchmark harness with:
make benchmarkmake benchmark-dry-runpython3 benchmarks/run.py --url http://localhost:8080 --input benchmarks/fixtures/faq_loop.jsonl --requests 500
- Development setup in
CONTRIBUTING.mdexpects 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, orintegration_test) rather than assuming per-file test targets. - Treat
README.mdas 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.mdfeature 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.mddocs-site/src/concepts/architecture-decisions.mddocs-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.
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.
- 8d ago First seen · 64 lines · 1,358 tokens per session scan A d19d6ebdaeb9
Isartor copilot-instructions.md is an instructions file published in the GitHub repository isartor-ai/Isartor (21 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,358 tokens to every session, about $0.0068 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
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.
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.
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).
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).
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.
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.