Borrowing it
Nothing to install: this file belongs to stufently/bing-webmaster-mcp. 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/stufently/bing-webmaster-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/stufently/bing-webmaster-mcpWrote 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/stufently/bing-webmaster-mcp/agents-md)<a href="https://agentmods.dev/instructions/stufently/bing-webmaster-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/stufently/bing-webmaster-mcp/agents-md/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/stufently/bing-webmaster-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/stufently/bing-webmaster-mcp/agents-md.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.00779 | $0.00779 |
| Opus 5.5 | $0.00312 | $0.00312 |
| Sonnet 5.5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
bing-webmaster-mcp 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 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working agreements for coding agents
Read SPEC.md first — it is the contract. This file is how to work in
the repo, not what to build.
Ground rules
- Do not invent API details. Method names, parameter shapes, quota numbers and
response formats come from a fetched Microsoft page or from
docs/api-surface.md, never from memory.SPEC.mdmarks every fact as verified or unverified; if you need something marked unverified, fetch it and update the marking in the same commit. - Never hardcode a quota. Read it from the API (
SPEC.md§9). - No network in tests. A test that reaches the internet is a broken test.
- No secrets in the repo. The API key comes from the environment. Never commit
a real key, a key-file name, or a site list.
.envstays ignored. - Every write goes through the apply boundary.
BING_WM_ALLOW_WRITESpicks whether a human sits between plan and apply, not whether the boundary exists. A mutating operation that reaches Bing without creating a plan record and passing throughapply_planis a bug, however it was invoked (SPEC.md§6). - Never add an apply or reject tool to the MCP server, in either mode. There is a test asserting their absence. If that test fails, the fix is to remove the tool, not to update the test. Enabling direct writes replaces the planning tools; it never adds a tool that can confirm a plan somebody else wrote.
Conventions
- Python ≥3.12, ruff (
line-length = 100,select = ["E","F","I","UP","B","SIM","S"]). - Dependency floors in
pyproject.toml, exact pins inconstraints.txt. Floors are lower bounds — do not raise one to the newest release just because it exists; that breaks every environment already running something older. - One
ops/module per domain. CLI and MCP both callops/, and neither holds logic of its own — if they can diverge in behaviour, the layering is wrong. - Error codes are a public contract. Adding one is fine; renaming one is a breaking change.
- Tests mirror modules 1:1.
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 · 58 lines · 779 tokens per session scan A c4e19686ff5c
bing-webmaster-mcp AGENTS.md is an instructions file published in the GitHub repository stufently/bing-webmaster-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 779 tokens to every session, about $0.0031 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-31.
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.