Borrowing it
Nothing to install: this file belongs to dynatrace-oss/dynatrace-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/dynatrace-oss/dynatrace-mcp/main/.github/instructions/typescript.instructions.mdgit clone --depth 1 https://github.com/dynatrace-oss/dynatrace-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/dynatrace-oss/dynatrace-mcp/typescript)<a href="https://agentmods.dev/instructions/dynatrace-oss/dynatrace-mcp/typescript"><img src="https://agentmods.dev/badge/instructions/dynatrace-oss/dynatrace-mcp/typescript.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.00797 | $0.00797 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
dynatrace-mcp typescript.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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server – TypeScript Agent Instructions
This document provides guidance for AI agents working on the TypeScript MCP server implementation. It covers the key concepts, patterns and conventions used in this project.
Reference Documentation
- Tools: https://modelcontextprotocol.io/docs/concepts/tools
- Tool Annotations: https://modelcontextprotocol.io/docs/concepts/tools#tool-annotations
- Resources: https://modelcontextprotocol.io/docs/concepts/resources
- Transports (stdio & Streamable HTTP): https://modelcontextprotocol.io/docs/concepts/transports
Project-Specific Patterns
console.error for Logging
Use console.error for all logging purposes in the MCP server code. This ensures that all log output is visible in the MCP host's log, which typically captures stderr output. Avoid using console.log as this prints to stdin, which is reserved for the MCP protocol communication and may not be visible in logs.
Implementing MCP Tools
Please refer to ./.github/instructions/mcp-tools.instructions.md for detailed instructions on implementing MCP tools in this codebase.
Capability Modules
Tools call capabilities (features), which live in src/capabilities/<feature-name>.ts. These files export plain async functions that accept an HttpClient and return data. They do not register tools themselves – that is done in src/index.ts.
src/capabilities/list-problems.ts ← pure business logic
src/index.ts ← tool registration using tool() helper
Follow this separation when adding new features:
- Create
src/capabilities/my-feature.tswith the core logic. - Import and register it in
src/index.tsusingtool().
Authentication – createAuthenticatedHttpClient
Use createAuthenticatedHttpClient(scopes) to get a Dynatrace HttpClient scoped to exactly the permissions required for the operation:
const dtClient = await createAuthenticatedHttpClient(['storage:logs:read', 'storage:entities:read']);
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 · 86 lines · 797 tokens per session scan A 7b6cb042cb19
dynatrace-mcp typescript.instructions.md is an instructions file published in the GitHub repository dynatrace-oss/dynatrace-mcp (136 stars, last pushed 11d ago), licensed MIT. It adds 797 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-30.
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.
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).