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/dynatrace-for-ai --skill dt-sec-semantic-mappinggit clone --depth 1 https://github.com/Dynatrace/dynatrace-for-aiWrote 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/dynatrace-for-ai/dt-sec-semantic-mapping)<a href="https://agentmods.dev/skills/dynatrace/dynatrace-for-ai/dt-sec-semantic-mapping"><img src="https://agentmods.dev/badge/skills/dynatrace/dynatrace-for-ai/dt-sec-semantic-mapping/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/dynatrace-for-ai/dt-sec-semantic-mapping"><img src="https://agentmods.dev/badge/skills/dynatrace/dynatrace-for-ai/dt-sec-semantic-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector pass
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.00069 | $0.01179 |
| Opus 5 | $0.00034 | $0.00589 |
| Sonnet 5 | $0.00014 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
dt-sec-semantic-mapping 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 12d 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.
dt-sec-semantic-mapping
Build and validate semantic-dictionary-aligned mappings for new security integrations.
Purpose
Use this skill when a user wants to:
- Suggest a mapping from vendor API output to Dynatrace
security.eventsfields (Workflow A). - Validate an existing mapping for completeness and quality against:
- Local baseline samples and semantic dictionary (Workflow B1 — static, offline validation), or
- Live tenant data via live tenant access (Workflow B2 — runtime validation)
- Highlight discrepancies vs. the Semantic Dictionary and local references.
- Get actionable mapping improvements.
Semantic Dictionary
The Semantic Dictionary (SD) defines the canonical field set for security.events. See references/semantic-reference.md for the canonical reference: local-vs-live sources, queryable Grail tables, when-to-query decision matrix, and the authority rule (live SD wins on disagreement).
Required Inputs
Always run the intake checklist in references/intake-and-constraints.md before generating or validating a mapping. If inputs are incomplete, continue with a partial draft but explicitly list missing evidence and confidence limits.
Baseline Sources (self-contained)
All baseline material lives inside this skill:
samples/— real integration payloads covering all finding types and providers. Consulted as a fallback when primary references (SD, data-model-notes, known-discrepancies, validation-rules, object-type-expectations) leave a specific question unresolved — not as a routine step on every workflow run.references/semantic-reference.md— SD reference, field taxonomy, event types, provider taxonomy, and entity scopingreferences/validation-policy-and-reporting.md— validation rules, acceptable discrepancies, and report templatesreferences/intake-and-constraints.md— intake checklist, output contract,object.typeexpectations, and OpenPipeline constraints
Event-Type Coverage Requirements
The mapping MUST address the correct set of event.type values per finding class. Detection integrations are push-based and do not use scan cycles — never require scan events for detection.
What ships with it
20 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/intake-and-constraints.md 35 KB
- references/mapping-workflow.md 13 KB
- references/runtime-validation.md 30 KB
- references/semantic-reference.md 28 KB
- references/validation-policy-and-reporting.md 62 KB
- samples/dynatrace-compliance-scans.json 2.3 KB
- samples/dynatrace-compliance.json 4.7 KB
- samples/dynatrace-detections-automated.json 4.4 KB
- samples/dynatrace-detections-rap.json 3.0 KB
- samples/dynatrace-vulnerabilities-change-events.json 15 KB
- samples/dynatrace-vulnerabilities-findings.json 6.2 KB
- samples/dynatrace-vulnerabilities-scans.json 3.5 KB
- samples/dynatrace-vulnerabilities-state-reports.json 20 KB
- samples/external-compliance.json 9.7 KB
- samples/external-detections.json 20 KB
- samples/external-threat-reports.json 7.8 KB
- samples/external-vulnerabilities-code-artifact.json 35 KB
- samples/external-vulnerabilities-container-image.json 24 KB
- samples/external-vulnerabilities-host.json 9.7 KB
- samples/external-vulnerabilities-scan.json 12 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.
- 12d ago First seen · 86 lines · 69 tokens per session scan A d92b574afc7e
dt-sec-semantic-mapping is a skill published in the GitHub repository Dynatrace/dynatrace-for-ai (137 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 1,179 once invoked, about $0.0003 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 skills, from other repositories
dtctl
Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems, root cause analysis, log patterns…
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.