Borrowing it
Nothing to install: this file belongs to israel-salgado/dt-mcp-server. 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/israel-salgado/dt-mcp-server/main/.agents/skills/dt-obs-tracing/SKILL.mdgit clone --depth 1 https://github.com/israel-salgado/dt-mcp-serverWrote 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/israel-salgado/dt-mcp-server/dt-obs-tracing)<a href="https://agentmods.dev/skills/israel-salgado/dt-mcp-server/dt-obs-tracing"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-obs-tracing/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/israel-salgado/dt-mcp-server/dt-obs-tracing"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-obs-tracing.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.00035 | $0.04443 |
| Opus 5 | $0.00017 | $0.02221 |
| Sonnet 5 | $0.00007 | $0.00889 |
| Haiku 4.5 | $0.00003 | $0.00444 |
Grade A, and why
dt-obs-tracing 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 — 641 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Tracing Skill
Overview
Distributed traces in Dynatrace consist of spans - building blocks representing units of work. With Traces in Grail, every span is accessible via DQL with full-text searchability on all attributes. This skill covers trace fundamentals, common analysis patterns, and span-type specific queries.
Core Concepts
Understanding Traces and Spans
Spans represent logical units of work in distributed traces:
- HTTP requests, RPC calls, database operations
- Messaging system interactions
- Internal function invocations
- Custom instrumentation points
Span kinds:
span.kind: server- Incoming call to a servicespan.kind: client- Outgoing call from a servicespan.kind: consumer- Incoming message consumption call to a servicespan.kind: producer- Outgoing message production call from a servicespan.kind: internal- Internal operation within a service
Root spans: A request root span (request.is_root_span == true) represents an incoming call to a service. Use this to analyze end-to-end request performance.
Key Trace Attributes
Essential attributes for trace analysis:
| Attribute | Description |
|---|---|
trace.id |
Unique trace identifier |
span.id |
Unique span identifier |
span.parent_id |
Parent span ID (null for root spans) |
request.is_root_span |
Boolean, true for request entry points |
request.is_failed |
Boolean, true if request failed |
duration |
Span duration in nanoseconds |
span.timing.cpu |
Overall CPU time of the span (stable) |
span.timing.cpu_self |
CPU time excluding child spans (stable) |
dt.smartscape.service |
Service Smartscape node ID |
dt.service.name |
Dynatrace service name derived from service detection rules. It is equal to the Smartscape service node name. |
endpoint.name |
Endpoint/route name |
Service Context
Spans reference services via Smartscape node IDs and the detected service name dt.service.name which is also present on every span.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/database-spans.md 4.2 KB
- references/entity-lookups.md 3.9 KB
- references/failure-detection.md 6.6 KB
- references/http-spans.md 4.7 KB
- references/logs-correlation.md 3.7 KB
- references/messaging-spans.md 3.6 KB
- references/networking-analysis.md 4.1 KB
- references/performance-analysis.md 3.0 KB
- references/request-attributes.md 4.6 KB
- references/rpc-spans.md 3.5 KB
- references/sampling-extrapolation.md 4.6 KB
- references/serverless-spans.md 4.1 KB
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 · 641 lines · 35 tokens per session scan A 38503936419a
dt-obs-tracing is a skill published in the GitHub repository israel-salgado/dt-mcp-server (2 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 4,443 once invoked, about $0.0002 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.