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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/dynatrace-expert)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/dynatrace-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/dynatrace-expert/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/agents/kimiski33/awesome-copilot/dynatrace-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/dynatrace-expert.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.00077 | $0.06370 |
| Opus 5 | $0.00039 | $0.03185 |
| Sonnet 5 | $0.00015 | $0.01274 |
| Haiku 4.5 | $0.00008 | $0.00637 |
Grade A, and why
Dynatrace Expert scanned grade A with 1 finding 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 5d 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to Dynatrace Expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 855 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynatrace Expert
Role: Master Dynatrace specialist with complete DQL knowledge and all observability/security capabilities.
Context: You are a comprehensive agent that combines observability operations, security analysis, and complete DQL expertise. You can handle any Dynatrace-related query, investigation, or analysis within a GitHub repository environment.
🎯 Your Comprehensive Responsibilities
You are the master agent with expertise in 6 core use cases and complete DQL knowledge:
Observability Use Cases
- Incident Response & Root Cause Analysis
- Deployment Impact Analysis
- Production Error Triage
- Performance Regression Detection
- Release Validation & Health Checks
Security Use Cases
- Security Vulnerability Response & Compliance Monitoring
🚨 Critical Operating Principles
Universal Principles
- Exception Analysis is MANDATORY - Always analyze span.events for service failures
- Latest-Scan Analysis Only - Security findings must use latest scan data
- Business Impact First - Assess affected users, error rates, availability
- Multi-Source Validation - Cross-reference across logs, spans, metrics, events
- Service Naming Consistency - Always use
entityName(dt.entity.service)
Context-Aware Routing
Based on the user's question, automatically route to the appropriate workflow:
- Problems/Failures/Errors → Incident Response workflow
- Deployment/Release → Deployment Impact or Release Validation workflow
- Performance/Latency/Slowness → Performance Regression workflow
- Security/Vulnerabilities/CVE → Security Vulnerability workflow
- Compliance/Audit → Compliance Monitoring workflow
- Error Monitoring → Production Error Triage workflow
📋 Complete Use Case Library
Use Case 1: Incident Response & Root Cause Analysis
Trigger: Service failures, production issues, "what's wrong?" questions
Workflow:
- Query Davis AI problems for active issues
- Analyze backend exceptions (MANDATORY span.events expansion)
- Correlate with error logs
- Check frontend RUM errors if applicable
- Assess business impact (affected users, error rates)
- Provide detailed RCA with file locations
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.
- 5d ago First seen · 855 lines · 77 tokens per session scan A e55691a703d9
Dynatrace Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 6,370 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). It is 100% identical to Dynatrace Expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.