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 skills add dynatrace-oss/dynatrace-managed-mcp --skill dynatrace-managedgit clone --depth 1 https://github.com/dynatrace-oss/dynatrace-managed-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/skills/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed)<a href="https://agentmods.dev/skills/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed/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/skills/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 138 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 140 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 142 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00101 | $0.01596 |
| Opus 5.5 | $0.00040 | $0.00638 |
| Sonnet 5.5 | $0.00020 | $0.00319 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
dynatrace-managed 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynatrace Managed
Guidance for driving the dynatrace-managed MCP server. The server sends its own detailed tool
instructions on connect - this skill covers what it cannot: getting it configured, and adapting
queries to this repository's own components and tagging strategy.
First: is it configured?
The server exits at startup unless exactly one configuration source is present. If tool calls fail
with Configuration not found, or dynatrace_managed_get_environments_info reports configuration
errors, the user needs to supply credentials - no amount of retrying will fix it.
When installed as a plugin, the client prompts for DT_ENVIRONMENT_CONFIGS up front and injects it
into the server, so this is usually already handled. Outside that flow there are two mutually
exclusive options, in priority order:
DT_CONFIG_FILE- path to a JSON or YAML file describing the environments. Preferred for more than one cluster. WriteapiToken: ${DT_PROD_TOKEN}and the loader interpolates that variable at runtime, so the file itself stays free of secrets and can be committed.DT_ENVIRONMENT_CONFIGS- a JSON array as a single environment variable. Preferred for one cluster and for containerized setups.
Setting both logs a warning and DT_CONFIG_FILE wins.
Minimal DT_ENVIRONMENT_CONFIGS value:
[
{
"alias": "production",
"apiEndpointUrl": "https://dynatrace.example.com",
"environmentId": "abc12345-1234-1234-1234-123456789abc",
"apiToken": "dt0c01...."
}
]
The API token needs read-only scopes. Point the user at docs/api_token_scopes.md rather than guessing which scopes a given tool requires, and at docs/environment_variables.md for the full variable list.
Never write a real API token into a file that is tracked by git, and never echo one back in chat.
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.
- 1mo ago Changed ae88840e03bb
- 2mo ago First seen · 147 lines · 101 tokens per session scan A 148b15fdbfb4
dynatrace-managed is a skill published in the GitHub repository dynatrace-oss/dynatrace-managed-mcp (33 stars, last pushed 4d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,596 once invoked, about $0.0004 per session on Opus 5.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-09-04.
Other skills, from other repositories
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
observability-expert
Use this server as the control plane for the unified fleet PLG stack (Grafana 12000, Prometheus 12001, Loki 12002).
pilot-log-analytics-setup
Deploy a log analytics system with 4 agents for collection, parsing, alerting, and visualization. Use this skill when: 1. User wants to set up centralized log collection with parsing, anomaly detection, and dashboards 2. User is configuring agents for log aggregation, error pattern analysis, or log-based alerting 3.…
Observability with Prometheus & Grafana
Production-grade observability stack with Prometheus metrics, Grafana dashboards, PromQL query language, alerting rules, and AI-powered anomaly detection for modern cloud-native applications.
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
clawmetry-selfcheck
Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task. Use when ClawMetry is installed on this machine and you want to check whether you are re-reading files, spinning in loops, or burning budget.