Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/gafoor2005/lam-mcp/copilot-instructionsgit clone --depth 1 https://github.com/Gafoor2005/LAM-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/gafoor2005/lam-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/gafoor2005/lam-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/gafoor2005/lam-mcp/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.00802 | $0.00802 |
| Opus 5 | $0.00401 | $0.00401 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
LAM-mcp 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation MCP Server
This project provides a Model Context Protocol (MCP) server for browser automation using Python and Selenium WebDriver, enabling intelligent web interactions with session-based context analysis.
Features
- Web navigation and page interactions
- Element clicking, typing, and form handling
- Page content extraction and scraping
- Screenshot capture
- JavaScript execution
- Cookie and session management
- Multi-browser support (Chrome, Firefox, Edge)
- Headless and headed browser modes
- Session-based context analysis for smart element identification
- Semantic search to find relevant page sections
- Context-aware element suggestions with confidence scores
- Progress tracking for automation sessions
Setup
- Install Python dependencies:
uv add mcp selenium webdriver-manager chromadb sentence-transformers - Install browser drivers automatically via webdriver-manager
- Configure the server in your MCP client (Claude Desktop, VS Code, etc.)
Tools Available
Session Context Intelligence
analyze_current_page: Analyze page structure and store in session contextfind_page_context: Find relevant page sections for your task using semantic searchget_smart_element_selector: Get elements with surrounding context for better identificationtrack_action_result: Track actions and success/failure in current sessionget_session_progress: View session statistics, actions taken, and success rateclear_session_context: Clear session memory and start fresh
Core Automation
navigate_to_url: Navigate to a specific URLclick_element: Click on page elements by selectortype_text: Type text into input fieldsextract_text: Extract text content from elementstake_screenshot: Capture page screenshotsexecute_javascript: Run JavaScript codeget_page_source: Get full HTML sourcefill_form: Fill out web formsscroll_page: Scroll the pagewait_for_element: Wait for elements to appearget_cookies: Retrieve page cookiesset_cookies: Set browser cookies
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 · 99 lines · 802 tokens per session scan A 2beffd6d524a
LAM-mcp copilot-instructions.md is an instructions file published in the GitHub repository Gafoor2005/LAM-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 802 tokens to every session, about $0.0040 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
Browser4 CLAUDE.md
Claude Code instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
cc-websearch CLAUDE.md
Claude Code instructions for Djarvur/cc-websearch, covering project, constraints, technology stack, what not to add and conventions.
fix-quera AGENTS.md
Instructions for AlirezaKeshavarz83/fix-quera, covering agent guidance, project shape, visual style, quera page data findings and compatibility findings.
sniff AGENTS.md
AGENTS.md instructions for Aboudjem/sniff, covering agents.md: sniff, what this repo is, how an agent should use sniff, handling the playwright setup gate and finding output schema.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
sendblue-browser-use AGENTS.md
Instructions for sendblue-api/sendblue-browser-use, covering agents.md — sendblue-browser-use, what this repo is, setup, common commands and health (no auth).