verify-recent-trace

verify-recent-trace is a skill for Claude Code from honeycombio/agent-skill. It costs 47 tokens per session (777 once invoked), scanned A, original, MIT.

A guide for finding and inspecting a recent application trace in Honeycomb. A trace is the connected record of one request as it moves through the services that handle it.

In plain words
What is it for?
Use it to query recent traces, retrieve the newest matching example, and report the query, root operation, number of spans, and services involved.
Why use it?
It provides a consistent way to confirm that a recent test produced the expected trace and to see which services and operations were involved.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the honeycomb plugin — 11 skills, 1 command, 2 agents, 2 hooks shipped together

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.

agentmods
npx agentmods add skills/honeycombio/agent-skill/verify-recent-trace
Any agent
npx skills add honeycombio/agent-skill --skill verify-recent-trace
Clone the repo
git clone --depth 1 https://github.com/honeycombio/agent-skill

Made for: Claude Code.

Or install honeycomb, the plugin that ships this one along with the rest of its 11 skills, 1 command, 2 agents, 2 hooks.

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 verify-recent-trace

README.md
[![agentmods](https://agentmods.dev/badge/skills/honeycombio/agent-skill/verify-recent-trace.svg)](https://agentmods.dev/skills/honeycombio/agent-skill/verify-recent-trace)
Your own site
<a href="https://agentmods.dev/skills/honeycombio/agent-skill/verify-recent-trace"><img src="https://agentmods.dev/badge/skills/honeycombio/agent-skill/verify-recent-trace.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00047 $0.00777
Opus 5 $0.00023 $0.00388
Sonnet 5 $0.00009 $0.00155
Haiku 4.5 $0.00005 $0.00078

Measured 6d ago against content hash 8c935ba788dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

verify-recent-trace 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 6d 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.

honeycomb/skills/verify-recent-trace/SKILL.md · 120 lines

How it starts

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

Honeycomb Verification Skill

Purpose

Query Honeycomb to find the traces that were created by a recent test.

When to Use

This skill is automatically activated when:

  • User asks to "show me a trace in Honeycomb"
  • Completing an implementation step that requires observability verification

Verification Output

Report query results as: Queried [VIZ] where [FILTERS] by [GROUP_BY] over [TIME_RANGE] Results: [link to Honeycomb query]

Query Patterns

  • Time Range: 1200 seconds (20 minutes) - adjustable based on when the test started

Pattern 1: Get a particular trace

What service are you testing? This determines the dataset. Do you know the name of the span you expect to see?

Query for:
- dataset: [dataset]
- filter: name = [expected span name]
- time_range: [calculated time range]
- calculation: COUNT
- include_samples: true

Now take the most recent sample, and use get_trace to get the full trace. Output:

Queried [CALCULATION] where [FILTERS] over [TIME_RANGE] Found [count] results Results: [link to the query]

Most recent trace: [link to the trace] Root span: [root span name] Total spans: [count of spans] Services: [list of services]

Pattern 2: Find all traces since the test started

Query for:
- all datasets
- filter: trace.parent_id does-not-exist
- time_range: [calculated time range]
- calculation: COUNT
- breakdowns: name
- include_samples: true

Output: Queried [CALCULATION] where [FILTERS] by [BREAKDOWNS] over [TIME_RANGE] Found [count] results Results: [link to the query]

For each sample, print:

Pattern 3: Find the most recent trace, precisely

Query for:
  calculated_fields: event_time=EVENT_TIMESTAMP()
  calculation: COUNT
  breakdowns: event_time, trace.trace_id
  order: event_time DESC
  limit: 1
  include_samples: false

Read the full file on GitHub · 120 lines

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. 6d ago First seen · 120 lines · 47 tokens per session scan A 8c935ba788dd

Subscribe to this mod's changes

verify-recent-trace is a skill published in the GitHub repository honeycombio/agent-skill (22 stars, last pushed 9d ago), licensed MIT. It adds 47 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 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-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens