Borrowing it
Nothing to install: this file belongs to joe-elliott/tempo-llm-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joe-elliott/tempo-llm-cli/main/CLAUDE.mdgit clone --depth 1 https://github.com/joe-elliott/tempo-llm-cliWrote 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/instructions/joe-elliott/tempo-llm-cli/claude-md)<a href="https://agentmods.dev/instructions/joe-elliott/tempo-llm-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/joe-elliott/tempo-llm-cli/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00604 | $0.00604 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
tempo-llm-cli CLAUDE.md 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tempo LLM CLI
A specialized command-line interface that uses Claude to help explore and analyze distributed tracing data from Grafana Tempo.
Overview
This Go application provides an AI-powered interface for exploring tracing data using Tempo's API. Claude is equipped with specialized tools to query traces, analyze metrics, and understand distributed system behavior through TraceQL queries.
Building
# Build the application
go build -o tempo-llm-cli
# Or run directly
go run .
Usage
# Start an AI-powered tracing exploration session
./tempo-llm-cli
Once running, you can ask Claude natural language questions about your tracing data, such as:
- "Show me the slowest traces for the payment service"
- "What are the most common error patterns?"
- "How many requests per minute are we seeing?"
Environment Variables
Set your Anthropic API key:
export ANTHROPIC_API_KEY=your_api_key_here
Optionally configure the MCP server URL (defaults to http://localhost:3200/api/mcp):
export MCP_SERVER_URL=http://localhost:3200/api/mcp
Features
- AI-powered natural language queries for tracing data
- Interactive exploration of distributed system behavior
- Full conversation context preservation for complex analysis
- Graceful exit with 'quit' or 'exit' commands
- Error handling for API failures
Available Tools
Claude has access to specialized tools for tracing analysis:
- TraceQL Search: Find specific traces using TraceQL queries
- TraceQL Metrics: Generate metrics and aggregations from trace data
- Attribute Discovery: Explore available attributes and their values
- Trace Retrieval: Get detailed information about specific traces
- Documentation Access: Built-in TraceQL and Tempo documentation
Architecture
The application uses Claude's Messages API with conversation history maintained locally. Each message is sent with the complete conversation context to ensure coherent multi-turn conversations.
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 · 84 lines · 604 tokens per session scan A 2d50e33ad92f
tempo-llm-cli CLAUDE.md is an instructions file published in the GitHub repository joe-elliott/tempo-llm-cli (5 stars, last pushed 1y ago), licensed Apache-2.0. It adds 604 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.