Borrowing it
Nothing to install: this file belongs to icemage001/local_sharepoint_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/icemage001/local_sharepoint_mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/icemage001/local_sharepoint_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/icemage001/local_sharepoint_mcp/agents-md)<a href="https://agentmods.dev/instructions/icemage001/local_sharepoint_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/icemage001/local_sharepoint_mcp/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.00471 | $0.00471 |
| Opus 5 | $0.00235 | $0.00235 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
local_sharepoint_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 7d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a local MCP server and Chromium extension for SharePoint Online. Treat the implementation and its tests as the current capability contract; the files under docs/superpowers/ are historical planning material.
Safety Rules
- Keep the active-site lock explicit before every SharePoint write.
- Use the matching
preview_*tool before deletes, updates, permission changes, or formatting changes; apply only its returnedpreviewId. - Never print browser tokens or commit
data/*.json. Token audit data must remain token-free. - Do not expose the local bridge beyond
127.0.0.1. - Do not alter business lists, pages, or permissions during verification without the user's explicit target and approval.
- For real-site checks, use clearly named test artifacts, verify the result by API readback and UI inspection, and report any visual mismatch.
API and Token Rules
- Prefer Microsoft Graph for lists, list items, columns, drives, and modern pages when a valid Graph token is captured.
- Use SharePoint REST for groups, permissions, views, and view or column formatting.
- A SharePoint REST token cannot substitute for a Graph token. If a Graph-backed tool reports no token, refresh or navigate the SharePoint page and capture a fresh Graph request.
- The extension may capture only one resource audience on a given page load; inspect
get_healthbefore assuming a tool surface is available.
Current Limits
- Page tools cover list, get, create, layout preview/apply, and publish only. Do not claim page deletion or WebPart CRUD support.
- Gallery view JSON can be persisted through REST, but verify its rendered appearance in SharePoint. A saved formatter is not proof of a visual change.
- The real-site scripts target
CN_BX_Siteand require explicit environment-variable opt-in. They intentionally create persistent, timestamped test artifacts.
Validation
Run npm run check for repository changes. Real-site scripts are opt-in only:
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.
- 7d ago First seen · 37 lines · 471 tokens per session scan A d41e1d4bc4f8
local_sharepoint_mcp AGENTS.md is an instructions file published in the GitHub repository icemage001/local_sharepoint_mcp (1 stars, last pushed 25d ago), licensed MIT. It adds 471 tokens to every session, about $0.0024 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-31.
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.