Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dynatrace-oss/dynatrace-snowflake-observability-agentnpx agentmods add skills/dynatrace-oss/dynatrace-snowflake-observability-agent/qa-runnerWrote 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-oss/dynatrace-snowflake-observability-agent/qa-runner)<a href="https://agentmods.dev/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/qa-runner"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/qa-runner/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-oss/dynatrace-snowflake-observability-agent/qa-runner"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/qa-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00047 | $0.20502 |
| Opus 5.5 | $0.00019 | $0.08201 |
| Sonnet 5.5 | $0.00009 | $0.04100 |
| Haiku 4.5 | $0.00005 | $0.02050 |
Grade A, and why
qa-runner 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 1mo 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 — 2,252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: DSOA Release QA Runner
Use this skill when asked to:
- Start the QA process for a DSOA release
- Walk a QA engineer through the release test suite
- Deploy and open the QA test notebook
- Generate a QA signoff summary
Overview
The QA runner executes in five sequential phases. Complete each phase fully before moving to the next. Do not skip phases.
| Phase | Name | Who acts | Output |
|---|---|---|---|
| 1 | Version discovery | AI (automated) | Verified version tags + config files |
| 2 | Deployment guidance | Human (AI provides commands) | Both environments running |
| 3 | Notebook deployment | AI (runs script) | Notebook URL |
| 3.5 | Auto-evaluation | AI (runs DQL via MCP) | Pass/fail for auto-evaluable tests |
| 3.6 | Workflow deployment | AI + human gate | 10 workflows deployed + executed |
| 4 | Test walkthrough | Interactive | Pass/fail per checklist item |
| 5 | QA signoff | AI | Markdown report file |
Phase 1 — Version Discovery
Run all of the following automatically without waiting for the human.
1a. Determine current version
grep '^VERSION' src/dtagent/version.py | head -1
Store as CURR_VERSION (e.g. 0.9.4).
1b. Derive version tags
The 3-digit tag is: printf "%03d" $((minor * 10 + patch))
bash -c '
v="'"${CURR_VERSION}"'"
minor=$(echo "$v" | cut -d. -f2)
patch=$(echo "$v" | cut -d. -f3)
printf "%03d\n" $(( minor * 10 + patch ))
'
Store as CURR_TAG (e.g. 094). The deployment environment is DEV-${CURR_TAG}.
1c. Determine previous version
Default rule: decrement the patch component of CURR_VERSION by 1.
Example: 0.9.4 → 0.9.3 → tag 093.
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.
- 1mo ago First seen · 2,252 lines · 47 tokens per session scan A 55f528265868
qa-runner is a skill published in the GitHub repository dynatrace-oss/dynatrace-snowflake-observability-agent (10 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 20,502 once invoked, about $0.0002 per session on Opus 5.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-09-02.
Other skills, from other repositories
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
testing-and-ci
Choose and run unit, E2E, Caddyfile fixture, automation, and CI checks for caddy-security. Use for coverage requirements, test evidence, failures, and report workflows; official OP conformance remains opt-in.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.