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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/benjisho/windows-mtr/agents-md"><img src="https://agentmods.dev/badge/instructions/benjisho/windows-mtr/agents-md.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.00605 | $0.00605 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
windows-mtr 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 4d 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.
AGENTS.md
Codex operating notes for windows-mtr (repository scope).
Mission and guardrails
- Keep
windows-mtrreliable, secure, and predictable for network diagnostics. - Prefer small, reviewable pull requests with clear user impact.
- Preserve CLI compatibility unless a change is explicitly requested and documented.
Required workflow
- Read context first:
README.md,USAGE.md, and touched source/tests/docs. - Plan a minimal safe diff (avoid unrelated refactors).
- Implement with explicit error handling and no silent network fallbacks.
- Validate with relevant checks.
- Update docs/changelog when behavior, UX, install, API, or release flow changes.
Repository map
src/— application code.tests/— integration/unit/report tests.examples/— sample usage.xtask/— automation helpers.docs/— project documentation.
Toolchain and validation
- Rust/toolchain expectations follow repo docs and CI (currently Rust 1.88.0+ / MSRV from
Cargo.toml). - For Rust changes, run when available:
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo test --all
- For workflow/docs hygiene changes, run targeted checks (for example
pre-commit run --all-files,actionlint, markdown lint). - If a command cannot run, report the exact command and concrete environment blocker.
API/OpenAPI checks (when API contract/spec changes)
python3 scripts/validate_openapi_schema.pyscripts/check_openapi_compat.sh <base-ref>
Security and sensitive-change caution
- Treat CLI args, hostnames, packet data, and files as untrusted inputs.
- Avoid logging sensitive data or adding telemetry/data-exfil behavior.
- Keep dependencies minimal and justified.
- Use extra care and minimal diffs for:
.github/workflows/**, release/version/tagging/packaging automation.- Security policy/audit/dependency configuration.
Documentation expectations
Update docs when changing:
- CLI flags/options/defaults.
- Output/report/API schema.
- Build/install/run/release behavior.
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.
- 4d ago First seen · 63 lines · 605 tokens per session scan A 6a04c9a5a992
windows-mtr AGENTS.md is an instructions file published in the GitHub repository benjisho/windows-mtr (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 605 tokens to every session, about $0.0030 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
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).
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 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.
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.