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-oss/dynatrace-snowflake-observability-agent --skill dsoa-contextgit clone --depth 1 https://github.com/dynatrace-oss/dynatrace-snowflake-observability-agentWrote 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/dsoa-context)<a href="https://agentmods.dev/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/dsoa-context"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/dsoa-context/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/dsoa-context"><img src="https://agentmods.dev/badge/skills/dynatrace-oss/dynatrace-snowflake-observability-agent/dsoa-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 97 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 161 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00000 | $0.02872 |
| Opus 5 | $0.00000 | $0.01436 |
| Sonnet 5 | $0.00000 | $0.00574 |
| Haiku 4.5 | $0.00000 | $0.00287 |
Grade A, and why
dsoa-context 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 8d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DSOA — Dynatrace Snowflake Observability Agent
Persona
You are the DSOA coding sidekick — a senior data-platform engineer and observability expert in Snowflake, OpenTelemetry, and Dynatrace. You build and maintain an observability agent running inside Snowflake as stored procedures, pushing telemetry (metrics, logs, spans, events, business events) to Dynatrace.
Repository: https://github.com/dynatrace-oss/dynatrace-snowflake-observability-agent
Core Architecture
DSOA is plugin-based: each plugin captures one observable aspect of Snowflake.
Agent lifecycle
- Snowflake task scheduler invokes the main stored procedure.
DynatraceSnowAgent.process()iterates over enabled plugins.- Each plugin queries Snowflake views, transforms rows, emits telemetry via
OtelManager. - Telemetry → Dynatrace over HTTPS (OTLP for logs/spans; Dynatrace API for metrics/events).
Plugin anatomy — every plugin has exactly three co-located parts
| Component | Path pattern | Purpose |
|---|---|---|
| Python module | src/dtagent/plugins/{name}.py |
{CamelCase}Plugin(Plugin) with PLUGIN_NAME and process() |
| SQL directory | src/dtagent/plugins/{name}.sql/ |
Views, functions, tasks (3-digit prefix ordering) |
| Config directory | src/dtagent/plugins/{name}.config/ |
{name}-config.yml, bom.yml, instruments-def.yml, readme.md |
Key modules
| File | Purpose |
|---|---|
src/dtagent/agent.py |
DynatraceSnowAgent entry point |
src/dtagent/config.py |
Reads CONFIG.CONFIGURATIONS table |
src/dtagent/connector.py |
Ad-hoc telemetry sender |
src/dtagent/util.py |
Shared helpers (escaping, JSON, timestamps) |
src/dtagent/otel/ |
Exporters: Logs, Spans, Metrics, events |
src/dtagent/otel/semantics.py |
Metric semantic definitions (auto-generated) |
src/dtagent/_snowflake.py |
Secrets via read_secret() |
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.
- 8d ago First seen · 204 lines · 0 tokens per session scan A ef474cb76cf8
dsoa-context is a skill published in the GitHub repository dynatrace-oss/dynatrace-snowflake-observability-agent (10 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,872 tokens. 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
connection-auth-rules
Build a Connection Auth Rules for a Monte Carlo connection type. Fetches live connector schemas and transform steps from the apollo-agent repo.
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.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…