agentmods.dev

doca-telemetry-traceback-application

doca-telemetry-traceback-application is a skill for Claude Code, Codex from NVIDIA/skills. It costs 207 tokens per session (2,966 once invoked), scanned A, original, Apache-2.0.

A monitoring application for telemetry on a BlueField DPU or ConnectX network card. It watches measurements over time, checks user-defined thresholds, and records data from before and during an event in a log.

In plain words
What is it for?
Use it to configure telemetry rules, monitor long-term trends, investigate empty event logs, and capture the data around an alert.
Why use it?
It helps you detect slow changes and threshold breaches without handling every raw measurement yourself. The saved pre-event history can show what led up to a problem.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

not rated 3.9krepo +65 yesterday A scan 207 tokens original Apache-2.0

Good fit Use it to configure telemetry rules, monitor long-term trends, investigate empty event logs, and capture the data around an alert.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nvidia/skills/doca-telemetry-traceback-application
View source ↗ NVIDIA/skills docs.nvidia.com
About the project

NVIDIA/skills is a catalogue of portable instruction sets that teach coding agents how to use NVIDIA software for robotics, simulation, CUDA, retrieval-augmented generation, and related workflows. Developers install these skills in agents such as Claude Code or Codex, while the catalogue mirrors skills maintained in separate NVIDIA product repositories.

NVIDIA/skills · 3,873 stars · on GitHub · docs.nvidia.com

Install

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.

Any agent
npx skills add NVIDIA/skills --skill doca-telemetry-traceback-application
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for doca-telemetry-traceback-application

README.md
[![agentmods](https://agentmods.dev/badge/skills/nvidia/skills/doca-telemetry-traceback-application/github.svg)](https://agentmods.dev/skills/nvidia/skills/doca-telemetry-traceback-application)
Your own site
<a href="https://agentmods.dev/skills/nvidia/skills/doca-telemetry-traceback-application"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-telemetry-traceback-application/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.

agentmods 80×15 button for doca-telemetry-traceback-application

Your own site · 80×15
<a href="https://agentmods.dev/skills/nvidia/skills/doca-telemetry-traceback-application"><img src="https://agentmods.dev/badge/skills/nvidia/skills/doca-telemetry-traceback-application.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 207 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00207 $0.02966
Opus 5.5 $0.00083 $0.01186
Sonnet 5.5 $0.00041 $0.00593
Haiku 4.5 $0.00021 $0.00297

Measured 9d ago against content hash 94d5cb1d0915, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doca-telemetry-traceback-application 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 9d 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.

skills/doca-telemetry-traceback-application/SKILL.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DOCA Telemetry Traceback Application

Scope boundaries

These requests are out of scope: say so, name the skill that owns the request, and stop.

  • the DOCA Telemetry Diag programming API and raw counter reads: doca-telemetry/SKILL.md.
  • DOCA install and bring-up: doca-setup/SKILL.md.
  • which DOCA version is installed, version consistency: doca-version/SKILL.md.
  • general DOCA orientation and documentation lookup: doca-public-knowledge-map/SKILL.md.

Examples

  • “Can I monitor telemetry trends on the DPU without streaming all raw data?” — in scope. Configure rules and sample history depth; do not use the DOCA Telemetry Diag API directly here.
  • “The event log is empty even though a threshold was crossed.” — check rule comparison_type and sample_history_depth; differential rules require depth samples before functioning.
  • “How do I build only this application?” — use the Meson isolation flags; see the tasks companion.
  • “I'm writing my own C code against the DOCA Telemetry Diag library to read counters.” — that part is doca-telemetry's: the application uses Diag internally, but programming the Diag API is not this skill. Name doca-telemetry for it and do not write Diag API code here; handle every other part of the request as this skill describes (for example, --force-ownership still goes through doca-hardware-safety).

Quick facts

The authoritative source for the binary name, flags, and paths is the public DOCA Telemetry Traceback guide for the release; confirm them with the installed tool's --help before quoting any of them. As that guide describes it:

  • Standalone application on a BlueField DPU or ConnectX NIC; four components: DOCA Telemetry Diag instance, sample history circular buffer, rule collection, and events log file.
  • Configuration JSON fields: diag_sample_period_ns, sample_history_depth, data-ids array, and rules array. Rule types are incremental_greater_than (inc_gt), differential_greater_than (dt_gt), differential_less_than (dt_lt), greater_than (gt), and less_than (lt).
  • The circular buffer size is automatically doubled based on the requested depth to ensure equal historical and active event data.
  • Requires sudo/root privileges; mandatory -d PCIe address and -r rules JSON; optional --event-log and --force-ownership.
  • Unsupported data IDs are reported; adjust inputs accordingly.
  • The application stops if the actual sample size or period does not match the requested parameters.
  • --force-ownership changes diag domain ownership; route any use of it through doca-hardware-safety/SKILL.md.

Read the full file on GitHub · 244 lines

Files

What ships with it

7 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.

Changes

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.

  1. 9d ago First seen · 244 lines · 207 tokens per session scan A 94d5cb1d0915

Subscribe to this mod's changes

doca-telemetry-traceback-application is a skill published in the GitHub repository NVIDIA/skills (3,873 stars, last pushed yesterday), licensed Apache-2.0. It adds 207 tokens to every session and 2,966 once invoked, about $0.0008 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-10-29.

Analytics and metricsClaude CodeHardware and IoTagent-skillsagentic-aiai-agentscodexcoding-agents
Related

doca-telemetry-traceback-application compared with skills from other repositories

doca-telemetry-traceback-application next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
doca-telemetry-traceback-applicationNVIDIA/skillsSkill3.9kyesterdayApache-2.0A207Claude Code, Codex
desktop-and-local-ipc-securitymakifbaysal/tasktrooperSkill12016d agoApache-2.0A78Claude Code, Codex
spark-environment-setupwshobson/agentsSkill42kyesterdayMITA76Claude Code
spark-training-gotchaswshobson/agentsSkill42kyesterdayMITA63Claude Code
technical-troubleshootingstrands-agents/samplesSkill925yesterdayApache-2.0A38Claude Code
screen-mockup-htmlmakifbaysal/tasktrooperSkill12016d agoApache-2.0A63Claude Code, Codex
responsive-layoutmakifbaysal/tasktrooperSkill12016d agoApache-2.0A35Claude Code, Codex