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 agentmods add agents/viksant/vibe-coding-tools-content/distributed-tracing-engineergit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWrote 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/agents/viksant/vibe-coding-tools-content/distributed-tracing-engineer)<a href="https://agentmods.dev/agents/viksant/vibe-coding-tools-content/distributed-tracing-engineer"><img src="https://agentmods.dev/badge/agents/viksant/vibe-coding-tools-content/distributed-tracing-engineer.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.00006 | $0.03001 |
| Opus 5 | $0.00003 | $0.01501 |
| Sonnet 5 | $0.00001 | $0.00600 |
| Haiku 4.5 | $0.00001 | $0.00300 |
Grade A, and why
distributed-tracing-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -G http://localhost:16686/api/traces --data-urlencode "service=your_service_name" 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.
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.
- 2d ago First seen · 287 lines · 6 tokens per session scan A 326ce604cc51
distributed-tracing-engineer is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 6 tokens to every session and 3,001 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
json-fixer
Role: Apply targeted fixes from validator report. Patch specific fields, never regenerate from scratch. Support max 3 validation cycles.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
security-engineer
OWASP, access control, threat modeling.
bug-analyzer
Analyze root cause of bugs after location is identified. Second step in bug investigation.