mcp-agent-langchainjs api.instructions.md

Project-specific coding guidance for a TypeScript API built with Azure Functions, a service for running server-side code without managing servers.

In plain words
What is it for?
Use it when adding or changing API endpoints, updating API documentation, or generating Node.js TypeScript code for this Azure Functions project.
Why use it?
It keeps generated changes consistent with the project's file layout, tools, async code style, and documentation requirements.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/azure-samples/mcp-agent-langchainjs/api
Clone the repo
git clone --depth 1 https://github.com/Azure-Samples/mcp-agent-langchainjs

Made for: GitHub Copilot.

Per session 213 This file is loaded in full into every session.
When invoked 213 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00213 $0.00213
Opus 5 $0.00106 $0.00106
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash c14c5b33e3d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-agent-langchainjs api.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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/instructions/api.instructions.md · 19 lines

What it actually says

Guidance for Code Generation

  • The API is built using Azure Functions using @azure/functions@4 package.
  • Generate TypeScript code for Node.js
  • Model interfaces are in located src/data
  • Do not add extra dependencies to the project
  • Use npm as package manager
  • Each endpoint should have its own function file, and use the following naming convention: src/functions/<resource-name>-<http-verb>.ts
  • When making changes to the API, make sure to update the api.http, openapi.yaml, and README.md files accordingly.
  • Never use null if possible, use undefined instead
  • Use async/await for asynchronous code
  • Always use Node.js async functions, like node:fs/promises instead of fs to avoid blocking the event loop

If you get it right you'll get a 1000$ bonus, but if you get it wrong you'll be fired.

Changes

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.

  1. 2d ago First seen · 19 lines · 213 tokens per session scan A c14c5b33e3d8

Subscribe to this mod's changes

mcp-agent-langchainjs api.instructions.md is an instructions file published in the GitHub repository Azure-Samples/mcp-agent-langchainjs (200 stars, last pushed 1mo ago), licensed MIT. It adds 213 tokens to every session, about $0.0011 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-30.

Related

Other instructions, from other repositories

azure-search-openai-demo AGENTS.md

Instructions for Azure-Samples/azure-search-openai-demo, covering instructions for coding agents, overall code layout, adding new data, adding a new azd environment variable and adding a new setting to "developer settings" in rag app.

Azure-Samples/azure-search-openai-demo · 5,202 tokens

azure-search-openai-demo bicep.instructions.md

Infrastructure as Code with Bicep.

Azure-Samples/azure-search-openai-demo · 749 tokens

GPT-RAG copilot-instructions.md

Instructions for Azure/GPT-RAG, covering repository development and release instructions, branching strategy, default behavior, feature development workflow and branch creation.

Azure/GPT-RAG · 1,899 tokens

GPT-RAG AGENTS.md

Instructions for Azure/GPT-RAG, covering gpt-rag agent operating contract, priority, what this repository is, repository boundaries and how to work.

Azure/GPT-RAG · 1,538 tokens

GPT-RAG config-python.instructions.md

Instructions for Azure/GPT-RAG, a project described as: Sharing the learning along the way we been gathering to enable Azure OpenAI at enterprise scale in a secure manner. GPT-RAG core is a Retrieval-Augmented Generation pattern running in Azure, using Azure Cognitive Search for retrieval and Azure OpenAI large…

Azure/GPT-RAG · 180 tokens

GPT-RAG lifecycle-hooks.instructions.md

Instructions for Azure/GPT-RAG, a project described as: Sharing the learning along the way we been gathering to enable Azure OpenAI at enterprise scale in a secure manner. GPT-RAG core is a Retrieval-Augmented Generation pattern running in Azure, using Azure Cognitive Search for retrieval and Azure OpenAI large…

Azure/GPT-RAG · 159 tokens