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 skills add SigNoz/agent-skills --skill signoz-reducing-telemetry-costgit clone --depth 1 https://github.com/SigNoz/agent-skillsWrote 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/skills/signoz/agent-skills/signoz-reducing-telemetry-cost)<a href="https://agentmods.dev/skills/signoz/agent-skills/signoz-reducing-telemetry-cost"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-reducing-telemetry-cost/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.
<a href="https://agentmods.dev/skills/signoz/agent-skills/signoz-reducing-telemetry-cost"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-reducing-telemetry-cost.svg" alt="Reviewed on agentmods" width="80" 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.00157 | $0.05308 |
| Opus 5 | $0.00078 | $0.02654 |
| Sonnet 5 | $0.00031 | $0.01062 |
| Haiku 4.5 | $0.00016 | $0.00531 |
Grade A, and why
signoz-reducing-telemetry-cost 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 11d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
This skill calls SigNoz MCP server tools heavily (signoz_list_metrics,
signoz_get_field_keys, signoz_execute_builder_query,
signoz_get_top_metrics, signoz_check_metric_usage, signoz_check_metric_cardinality,
signoz_aggregate_logs, signoz_aggregate_traces, signoz_search_logs,
signoz_list_alert_rules, signoz_get_alert, signoz_get_service_top_operations). Before
running the workflow, confirm the signoz_* tools are available. If they are not, the SigNoz
MCP server is not installed or configured; run signoz-mcp-setup first. The whole
investigation is grounded in these queries; without the server there is nothing to analyze.
Read both reference files before drawing conclusions:
references/otel-attribute-cardinality.md: classify any metric label you encounter.references/infra-do-not-drop.md: the metrics that power the built-in Infrastructure page and the APM/Services page (span-derivedsignoz_*RED metrics); never present these as "safe to drop" even when usage shows them unused.
Workflow
Always start with the Cost Meter snapshot (Step 1). For a full cost investigation, run the metrics, logs, and traces steps for every signal with data, ordered by current cost contribution (primary, secondary, tertiary). Finish with the report (Step 5).
Step 1: Cost Meter snapshot
Establish the cross-signal cost picture first. Always call signoz_list_metrics with
source: "meter"; treat its returned metric names, types, temporalities, and units as the live
source of truth because the meter set evolves. Then query each relevant discovered metric with
signoz_execute_builder_query (source: "meter", requestType: "time_series",
stepInterval: 3600, the discovered temporality, and timeAggregation: "sum"); see
references/cost-meter-queries.md for the full tool-argument template. Sum complete hourly
buckets and exclude every datapoint marked partial: true. Do not use
signoz_query_metrics for Cost Meter totals or grouped total attribution.
Report only values returned by successful queries. If a query fails or returns no usable values
after the MCP tools are available, show the intended query and say that the total could not be
computed; never invent a total. If the tools are unavailable, follow the prerequisite instead.
What ships with it
4 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.
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.
- 11d ago First seen · 334 lines · 157 tokens per session scan A aaf6000bcd97
signoz-reducing-telemetry-cost is a skill published in the GitHub repository SigNoz/agent-skills (16 stars, last pushed 9d ago), licensed MIT. It adds 157 tokens to every session and 5,308 once invoked, about $0.0008 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.
Other skills, from other repositories
agent-observability
Instrument an LLM agent so failures are diagnosable, traces are replayable, and evals can run against production data. Use when the user is moving an agent past prototype and mentions tracing, spans, OpenTelemetry, LangSmith, Langfuse, Arize, OpenLLMetry, structured logs, GenAI semantic conventions, or asks "how do I…
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…