instrument-tracing

instrument-tracing is a skill for Claude Code from PostHog/ai-plugin. It costs 72 tokens per session (2,730 once invoked), scanned A, original, no licence file.

A workflow for adding PostHog distributed tracing to an application. Distributed tracing records a request as it moves through services, outgoing calls, and background jobs so its path and timing can be inspected.

In plain words
What is it for?
Use it after implementing features or reviewing pull requests to add or check tracing at request entry points, service calls, and background jobs.
Why use it?
It helps show where a request spends time and whether every important part of a feature produces a trace span.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the posthog plugin — 180 skills, 3 commands, 1 agent, 3 hooks, 1 MCP server shipped together

Good fit Use it after implementing features or reviewing pull requests to add or check tracing at request entry points, service calls, and background jobs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/posthog/ai-plugin/instrument-tracing
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 PostHog/ai-plugin --skill instrument-tracing
Clone the repo
git clone --depth 1 https://github.com/PostHog/ai-plugin

Made for: Claude Code.

Or install posthog, the plugin that ships this one along with the rest of its 180 skills, 3 commands, 1 agent, 3 hooks, 1 MCP server.

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 instrument-tracing

README.md
[![agentmods](https://agentmods.dev/badge/skills/posthog/ai-plugin/instrument-tracing/github.svg)](https://agentmods.dev/skills/posthog/ai-plugin/instrument-tracing)
Your own site
<a href="https://agentmods.dev/skills/posthog/ai-plugin/instrument-tracing"><img src="https://agentmods.dev/badge/skills/posthog/ai-plugin/instrument-tracing/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 instrument-tracing

Your own site · 80×15
<a href="https://agentmods.dev/skills/posthog/ai-plugin/instrument-tracing"><img src="https://agentmods.dev/badge/skills/posthog/ai-plugin/instrument-tracing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,730 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 unknown 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.00072 $0.02730
Opus 5.5 $0.00029 $0.01092
Sonnet 5.5 $0.00014 $0.00546
Haiku 4.5 $0.00007 $0.00273

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

Security

Grade A, and why

instrument-tracing 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 2d 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/instrument-tracing/SKILL.md · 115 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 115 lines · 72 tokens per session scan A c726b54d0690

Subscribe to this mod's changes

instrument-tracing is a skill published in the GitHub repository PostHog/ai-plugin (95 stars, last pushed yesterday), with no licence file. It adds 72 tokens to every session and 2,730 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

motherduck-build-cfa-app

Build MotherDuck analytics into customer-facing applications with tenant isolation, backend routing, and serving APIs.

motherduckdb/agent-skills · 26 tokens

motherduck-connect

Set up or troubleshoot MotherDuck connections, the MotherDuck MCP server in AI clients, authentication, client runtimes, and read scaling.

motherduckdb/agent-skills · 31 tokens

motherduck-rest-api

Administer MotherDuck service accounts, tokens, Ducklings, and Dive embed sessions through the control-plane REST API.

motherduckdb/agent-skills · 28 tokens

domscribe

Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…

patchorbit/domscribe · 94 tokens

gerrit-task-query

Use when asked to check, list, or act on tasks for a Gerrit change. Triggers on phrases like "what tasks are blocking", "which tasks are actionable", "check task status", "what do I need to do for this change", "what is blocking this change".

GerritCodeReview/gerrit-mcp-server · 64 tokens

forge-app-builder

Plan, build, scaffold, or safely extend Atlassian Forge apps using current official documentation. Use for fresh Forge apps, existing-app feature work, module and manifest changes, UI Kit or Custom UI implementation, backend functions and events, Atlassian or external APIs, storage, permissions, environment…

atlassian/forge-skills · 91 tokens