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 agentmods add instructions/dynatrace/dynatrace-workflow-samples/agents-mdgit clone --depth 1 https://github.com/Dynatrace/Dynatrace-workflow-samplesWrote 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/instructions/dynatrace/dynatrace-workflow-samples/agents-md)<a href="https://agentmods.dev/instructions/dynatrace/dynatrace-workflow-samples/agents-md"><img src="https://agentmods.dev/badge/instructions/dynatrace/dynatrace-workflow-samples/agents-md.svg" alt="Measured on agentmods" 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 | $0.08505 | $0.08505 |
| Opus 5 | $0.04253 | $0.04253 |
| Sonnet 5 | $0.01701 | $0.01701 |
| Haiku 4.5 | $0.00851 | $0.00851 |
Grade A, and why
Dynatrace-workflow-samples AGENTS.md 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --request POST 'https://{tenant}.apps.dynatrace.com/platform/automation/v1/workflows' \ How it starts
The opening of the file, as written. The whole thing — 1,204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynatrace Workflows - AI Assistant Instructions
This document provides comprehensive guidelines for creating syntactically correct Dynatrace Workflows. These instructions are designed for AI coding assistants including GitHub Copilot, Cursor, Claude Code, and Kiro.
Overview
Dynatrace Workflows are automation solutions that allow you to orchestrate tasks, integrate with external systems, and automate responses to events. This repository contains sample workflows and code snippets for the Dynatrace AutomationEngine and Workflows app.
Important: There are three distinct formats for Dynatrace Workflows. Never mix these formats:
- Workflow Templates (YAML) - For UI import/export
- API Format (JSON) - For programmatic workflow management
- Terraform/Monaco - For Configuration-as-Code deployments
Pull Request Review Guidelines
When reviewing pull requests (automated or manual), verify the following:
Workflow Syntax Validation
- Correct format used: YAML template, API JSON, or Terraform (never mixed)
- schemaVersion is 3: All workflows must use
schemaVersion: 3 - Valid YAML/JSON syntax: No parsing errors
- Task names match:
namefield inside task matches the task key - Predecessors exist: All referenced predecessor tasks are defined
- Actions are valid: Action names follow
app:actionpattern (e.g.,dynatrace.automations:execute-dql-query)
Security Review
- No hardcoded secrets: No API keys, tokens, passwords, or credentials in workflow files
- Use
secret()function: Sensitive values should use{{ secret('secret_name') }} - Use connections: External service credentials stored in Dynatrace connections
- No internal URLs exposed: No internal/private endpoints in HTTP actions
Best Practices
- Meaningful task names: Descriptive names like
fetch_security_logsinstead oftask1 - Task descriptions: Every task should have a description
- Proper error handling: Conditions check task states before proceeding
- Dependencies declared: All required apps listed in metadata dependencies
- File naming: Templates use
wftpl_*.yamlnaming convention
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 · 1,204 lines · 8,505 tokens per session scan A 2d03882dcfc1
Dynatrace-workflow-samples AGENTS.md is an instructions file published in the GitHub repository Dynatrace/Dynatrace-workflow-samples (19 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 8,505 tokens to every session, about $0.0425 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
agents AGENTS.md
AGENTS.md instructions for cloudflare/agents, covering agents.md, project overview, repository structure, nested agents.md files and setup.
open-agent-hub AGENTS.md
AGENTS.md instructions for guanyang/open-agent-hub, covering agents.md, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
dynatrace-mcp typescript.instructions.md
Instructions for dynatrace-oss/dynatrace-mcp, covering mcp server – typescript agent instructions, reference documentation, project-specific patterns, console.error for logging and implementing mcp tools.
dtctl CLAUDE.md
Claude Code instructions for dynatrace-oss/dtctl, a project described as: CLI for managing Dynatrace platform resources - built for humans and AI agents alike.
arc AGENTS.md
AGENTS.md instructions for howells/arc, covering arc, shape, gotchas, editing constraints and search order.
heym CLAUDE.md
Claude Code instructions for heymrun/heym, covering claude.md - combative directive ⚠️, 1. mandatory: load agents.md immediately ⚠️, 2. my ironclad rules, 3. session startup protocol and 4. alert system.