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 LerianStudio/ring --skill using-lib-observabilitygit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/using-lib-observability)<a href="https://agentmods.dev/skills/lerianstudio/ring/using-lib-observability"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/using-lib-observability.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 64 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00102 | $0.06594 |
| Opus 5 | $0.00051 | $0.03297 |
| Sonnet 5 | $0.00020 | $0.01319 |
| Haiku 4.5 | $0.00010 | $0.00659 |
Grade A, and why
ring:using-lib-observability 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 4d 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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ring:using-lib-observability
When to use
Sweep mode:
- "Sweep the codebase for lib-observability opportunities"
- "Find where we use raw zap / slog instead of lib-observability/log"
- "Audit OTel metric collectors and replace with MetricsFactory"
- "Find hand-rolled redaction or hard-coded OTel attribute strings"
Reference mode:
- "What does lib-observability provide for X?"
- "How do I initialize the logger for production vs local?"
- "What's the right way to create a counter / gauge / histogram?"
- "Which constants ship for OTel attributes/metric names/event names?"
- "How does redaction.IsSensitiveField decide what to mask?"
Skip when
- Working on non-Go services
- Working on frontend code
- Target codebase is Ring itself (no lib-observability dependency)
- Target package is
assert/,runtime/, ortracing/(see Related)
Related
Similar: ring:using-assert, ring:using-runtime, ring:using-tracing, ring:using-lib-commons
assert/ is owned by [[using-assert]] (production assertions).
runtime/ is owned by [[using-runtime]] (panic recovery telemetry).
tracing/ is owned by [[using-tracing]] (OTel trace SDK + processor).
This skill covers the foundation layer only: log, metrics, zap, redaction, constants.
Mode Selection
| Request Shape | Mode |
|---|---|
| "Sweep / audit / find DIY observability" | Sweep |
| "Replace our zap.New / slog setup with lib-observability" | Sweep |
| "What logger interface do we use?" | Reference |
| "How do I build a Counter with attributes?" | Reference |
"What constants exist for db.system etc?" |
Reference |
SWEEP MODE
Orchestrate a 3-phase sweep. Each phase has a hard gate — do not proceed until the current phase produces its artifact.
Phase 1: Version Reconnaissance → version-report.json
Phase 2: Multi-Angle DIY Sweep → 5 × libobs-sweep-{N}-{angle}.json
Phase 3: Consolidated Report → libobs-sweep-report.md + tasks.json
Phase 1: Version Reconnaissance
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.
- 4d ago First seen · 632 lines · 102 tokens per session scan A c627bdb79a18
ring:using-lib-observability is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 18d ago), licensed Apache-2.0. It adds 102 tokens to every session and 6,594 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
security-audit
Comprehensive .NET security audit — OWASP vulnerability scan, NuGet vulnerability check, secrets detection, and combined severity report.
api-doc-gen
Generate or update OpenAPI specification from .NET controller attributes. Validate spec-to-code consistency. Use after adding or changing API endpoints.
ds-backend
Backend architecture — API design, database schema, authentication, data pipelines. Use when designing or reviewing a backend, REST/GraphQL APIs, data models, auth flows, or ingest/ETL pipelines.
execution/backend-executor
Internal: Backend Executor. Implements API routes, services, business logic, auth. Read spec and segment. Write evidence on completion.
execution/integration-executor
Internal: Integration Executor. Wires components together, connects external APIs, handles plumbing. Write evidence on completion.
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.