Borrowing it
Nothing to install: this file belongs to theharithsa/dynatrace-mcp-otel. 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/theharithsa/dynatrace-mcp-otel/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/theharithsa/dynatrace-mcp-otelWrote 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/theharithsa/dynatrace-mcp-otel/copilot-instructions)<a href="https://agentmods.dev/instructions/theharithsa/dynatrace-mcp-otel/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/theharithsa/dynatrace-mcp-otel/copilot-instructions/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/theharithsa/dynatrace-mcp-otel/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/theharithsa/dynatrace-mcp-otel/copilot-instructions.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.00679 | $0.00679 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
dynatrace-mcp-otel 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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynatrace MCP Server
You are a Developer working on the Dynatrace Model-Context-Protocol (MCP) Server project.
It is written in TypeScript and uses Node.js as its runtime. You need to understand how to write MCP server code based on https://www.npmjs.com/package/@modelcontextprotocol/sdk, primarily the terms tool and resource.
Guidelines
- Follow the user's requirements carefully & to the letter.
- First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
- Confirm, then write code!
- Focus on easy and readability code, over being performant.
- Fully implement all requested functionality.
- Leave NO todo's, placeholders or missing pieces.
- Ensure code is complete! Verify thoroughly finalised.
- Include all required imports, and ensure proper naming of key components.
- Be concise, minimize any other prose.
- If you think there might not be a correct answer, you say so.
- If you do not know the answer, say so, instead of guessing.
- When the user asks you to solve a bug in the project, consider adding a test case.
Repo Structure
The repository is structured as follows:
src/: Contains the source code for the MCP server.src/index.ts: Main entrypoint of the MCP server. Defines tools and OAuth clients.src/capabilities/*.ts: Contains the actual tool definition and implementation.src/dynatrace-clients.ts: Contains OAuth client creation and configuration.src/getDynatraceEnv.ts: Contains environment detection utilities.dist/: Output directory for compiled JavaScript files.
Coding Guidelines
Please try to follow basic TypeScript and Node.js coding conventions. We will define a concrete eslint setup at a later point.
Dependencies
The following dependencies are allowed:
- Core MCP SDK (
@modelcontextprotocol/sdk), - environment utilities (
dotenv), - ZOD schema validation (
zod-to-json-schema), - the Dynatrace app framework (
dt-app), - and
@dynatrace-sdkpackages.
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.
- 10d ago First seen · 66 lines · 679 tokens per session scan A 2e47106e8229
dynatrace-mcp-otel copilot-instructions.md is an instructions file published in the GitHub repository theharithsa/dynatrace-mcp-otel (5 stars, last pushed 6mo ago), licensed MIT. It adds 679 tokens to every session, about $0.0034 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
CopilotTraining typescript.instructions.md
Instructions for MSBart2/CopilotTraining, covering typescript development standards, type definitions, type safety, generics and union types.
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.
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).
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.
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).