Borrowing it
Nothing to install: this file belongs to benjisho/windows-mtr. 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/benjisho/windows-mtr/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/benjisho/windows-mtrWrote 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/benjisho/windows-mtr/copilot-instructions)<a href="https://agentmods.dev/instructions/benjisho/windows-mtr/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/benjisho/windows-mtr/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.00460 | $0.00460 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
windows-mtr 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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for windows-mtr
These instructions guide GitHub Copilot and AI code assistants when proposing changes in this repository.
Project intent
- Keep
windows-mtrreliable, secure, and predictable for network diagnostics. - Preserve CLI compatibility unless a task explicitly documents a compatibility change.
- Favor small, reviewable diffs over broad rewrites.
Refactor policy (prune unsafe refactors)
- Prefer targeted fixes over structural refactors.
- Do not rename/move modules, change public CLI surface, or rework core probe/report flow unless explicitly requested.
- If a refactor is needed, include:
- scope boundaries,
- compatibility impact,
- rollback plan,
- focused tests proving parity.
Engineering expectations
- Follow nearby Rust patterns and naming.
- Use explicit, typed error paths and actionable user-facing messages.
- Treat CLI args, hostnames, packet data, and files as untrusted.
- Avoid silent network fallbacks and hidden retries.
- Avoid new dependencies unless justified in PR rationale.
Branch-delta review checklist (before coding)
- Review commit history and changed files to understand intent and drift.
- Identify what is complete vs what remains (tests, docs, compatibility notes).
- Confirm instructions still match current repository layout.
- Implement only the minimum required change set.
Required validation checks
Run what is available in the environment:
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all
If a check cannot run, state the exact blocker and never fabricate results.
Documentation discipline
Update docs when changing:
- CLI flags/options/defaults.
- Output/report schema.
- Build, install, release, or packaging flow.
Primary docs:
README.mdUSAGE.mdCHANGELOG.md(for user-facing behavior)docs/pages for workflow details
Pull request quality
PR descriptions should include:
- What changed.
- Why it changed.
- How it was validated (exact commands).
- Compatibility/risk notes.
- Follow-up work (if intentionally deferred).
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.
- 5d ago First seen · 62 lines · 460 tokens per session scan A ecad366308f4
windows-mtr copilot-instructions.md is an instructions file published in the GitHub repository benjisho/windows-mtr (10 stars, last pushed 4d ago), licensed Apache-2.0. It adds 460 tokens to every session, about $0.0023 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-09-02.
Other instructions, from other repositories
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).
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.
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).
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.