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-app-dashboards/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-app-dashboards)<a href="https://agentmods.dev/skills/israel-salgado/dt-mcp-server/dt-app-dashboards"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-app-dashboards/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-app-dashboards"><img src="https://agentmods.dev/badge/skills/israel-salgado/dt-mcp-server/dt-app-dashboards.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.00054 | $0.01991 |
| Opus 5 | $0.00027 | $0.00996 |
| Sonnet 5 | $0.00011 | $0.00398 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
dt-app-dashboards 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynatrace Dashboard Skill
Overview
Dynatrace dashboards are JSON documents stored in the Document Store. Each dashboard contains:
- Tiles: Visual components displaying markdown content or data visualizations
- Layouts: Grid-based positioning (20-unit width) defining tile placement
- Variables: Dynamic parameters (
$VariableName) for query filtering - Configuration: Version metadata and dashboard-level settings
When to use this skill:
- Creating new dashboards with skill-based query generation
- Modifying existing dashboards (queries, tiles, layouts)
- Querying dashboard JSON to extract data or analyze structure
- Analyzing dashboard purpose, metrics coverage, and health
Four main workflows:
- Creating - Build dashboards with skill-based queries
- Modifying - Update tiles, queries, layouts, variables
- Querying - Extract data from dashboard JSON
- Analyzing - Understand structure, purpose, gaps, and health
Dashboard Document Structure
Dashboards in the Dynatrace Document Store include both metadata and content:
{
"id": "dashboard-abc123",
"name": "My Dashboard",
"type": "dashboard",
"owner": "user-uuid",
"version": 60,
"modificationInfo": {...},
"content": {
"version": 21,
"variables": [],
"tiles": {...},
"layouts": {...}
}
}
Metadata (top-level):
.id- Document ID.name- Dashboard name.owner- Owner UUID.version- Document version (change tracking).modificationInfo- Creation/modification timestamps
Dashboard content (.content):
.content.version- Dashboard schema version (current: 21).content.tiles- Tile definitions.content.layouts- Tile positioning.content.variables- Dashboard variables
All jq examples in this skill use the .content.* paths.
When to Load References
This skill uses progressive disclosure - load only what you need:
- Start here: SKILL.md provides core concepts and quick-start examples
- Load references on-demand: Each reference file covers a specific deep-dive topic
- Context efficiency: Progressive loading enables task completion without external documentation
What ships with it
5 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.
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 · 238 lines · 54 tokens per session scan A 8249bb3951c4
dt-app-dashboards is a skill published in the GitHub repository israel-salgado/dt-mcp-server (2 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,991 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…