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/changelog.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/changelog)<a href="https://agentmods.dev/instructions/dynatrace-oss/dynatrace-mcp/changelog"><img src="https://agentmods.dev/badge/instructions/dynatrace-oss/dynatrace-mcp/changelog/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/dynatrace-oss/dynatrace-mcp/changelog"><img src="https://agentmods.dev/badge/instructions/dynatrace-oss/dynatrace-mcp/changelog.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.00579 | $0.00579 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
dynatrace-mcp changelog.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 11d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When releasing a new version, you will be asked to create a new section in the CHANGELOG.md file for the version based on "Unreleased Changes".
What belongs in the changelog
Only include changes that are relevant to end-users:
- New tools or features
- Bug fixes and reliability improvements
- Authentication or scope changes
- Breaking changes or migration guidance
- Dependency updates that fix security vulnerabilities
- Routine dependency updates (non-dev dependencies), summarized in a single line listing all updated packages with their old and new versions
Do not add entries for internal/technical changes that have no user-visible impact, such as:
- Refactoring or code cleanup
- Test additions or updates
- Documentation or instruction file updates
- Tooling and build configuration changes
- Dev-only dependency updates (e.g.,
vite,@types/*, test frameworks)
Style guidelines
- Use semantic versioning headings (e.g., ## )
- Release candidates are supported with a version suffix format (e.g.,
0.5.0-rc.1should be labeled as "0.5.0 (Release Candidate 1)" in the changelog) - Do not use subheadings
- Do not mention commit hashes, pull request numbers, or ticket IDs
- Write in past tense (e.g., "improved", "introduced", "added")
- Balance technical accuracy with user-facing language
- Use bullet points for individual changes
Content guidelines
- Entries should be concise but can include technical details relevant to users
- Write a bullet point for every new, changed, fixed, or removed feature
- No emojis
- Include both user benefits and technical specifics when relevant
- Use user-centric language ("You can now...", "You will now find...", "It is now possible to...")
- Explain business value ("enabling more precise...", "providing greater flexibility...", "ensuring smoother performance...")
Examples
- New tools/features: "Added [tool/feature name] [brief description]"
- Improvements: "Improved [component] to [specific enhancement]"
- Bug fixes: "Fixed [issue description]" or "Fixed: [specific problem]"
- Removals: "Removed [item] [reason if relevant]"
- Technical changes: Include scope changes, API modifications, and architectural improvements
- Dependency updates: "Updated
pkg-a(1.0.0 → 1.1.0),pkg-b(2.3.0 → 2.4.0), andpkg-c(0.5.1 → 0.6.0)." — all non-dev dependency updates in a single bullet point
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.
- 11d ago First seen · 53 lines · 579 tokens per session scan A e38740eeb926
dynatrace-mcp changelog.instructions.md is an instructions file published in the GitHub repository dynatrace-oss/dynatrace-mcp (136 stars, last pushed 15d ago), licensed MIT. It adds 579 tokens to every session, about $0.0029 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
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).
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.