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 neverinfamous/memory-journal-mcp --skill opentelemetrygit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/opentelemetry)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/opentelemetry"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/opentelemetry/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/neverinfamous/memory-journal-mcp/opentelemetry"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/opentelemetry.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.00070 | $0.00720 |
| Opus 5 | $0.00035 | $0.00360 |
| Sonnet 5 | $0.00014 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
opentelemetry 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry (OTel)
Production standards for instrumenting applications to achieve high-fidelity observability.
1. Distributed Tracing
- Trace Context Propagation: Always propagate the
traceparentandtracestateheaders across HTTP and RPC boundaries (using W3C Trace Context). - Span Granularity: Create spans for logical units of work. Avoid creating spans for every single function call (which causes overhead). Focus on:
- Incoming HTTP requests
- Database queries
- External API/LLM calls
- Background task executions
- Semantic Conventions: Use standardized span attributes (e.g.,
http.method,http.status_code,db.system). Do not invent custom attribute names when standard ones exist.
2. Span Implementation Guidelines
- Status and Errors: explicitly set the span status to
Errorwhen an exception occurs, and record the exception object on the span. - Payloads: Avoid logging sensitive PII or massive payloads in span attributes. Log structural identifiers (e.g.,
user.id,tenant.id).
// Example: Creating a Span in Node.js
tracer.startActiveSpan('database.query', (span) => {
try {
span.setAttribute('db.statement', queryText)
const result = db.execute(queryText)
span.setStatus({ code: SpanStatusCode.OK })
return result
} catch (error) {
span.recordException(error)
span.setStatus({ code: SpanStatusCode.ERROR, message: error.message })
throw error
} finally {
span.end()
}
})
3. Metrics
- RED Metrics: Focus on Rate (requests/sec), Errors (error rate), and Duration (latency distribution).
- Histograms over Summaries: Use Histograms for latency measurements to allow accurate percentile aggregations across distributed instances.
4. Exporters and Infrastructure
- OTLP Exporters: Always export telemetry using the OpenTelemetry Protocol (OTLP) via gRPC or HTTP to an OpenTelemetry Collector, rather than exporting directly to backend vendors (Datadog, Honeycomb) from the application.
- Batching: Use batch span processors (
BatchSpanProcessor) in production to minimize performance overhead. Only useSimpleSpanProcessorfor local debugging.
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.
- 10d ago First seen · 63 lines · 70 tokens per session scan A 46b2449f13d7
opentelemetry is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 720 once invoked, about $0.0003 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
tech-writing
Write professional technical documents — requirements/PRD, tech spec/design doc, low-level design, decision records, and trade-off analysis — at a formality tier matched to the task. Grounds every claim in real code or a cited source, marks what it could not verify, and refuses to pad. Use when asked to write/update a…
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb…
context-end
Close a workspace session by reviewing a proposed summary, recording approved outcomes, updating state and decisions, and checking repository safety. Use only when the user explicitly asks to end, close, or hand off the current session.
context-setup
Build, import, or refresh this workspace's identity, project, reusable-workflow, and weekly-state files through a guided review. Use only when the user explicitly asks to initialize or redo workspace context.
context-start
Load this workspace's current state, recent decisions, blockers, priorities, and session continuity, then give a concise briefing. Use only when the user explicitly asks to begin or resume a workspace session.
perf-profiling
Systematic performance profiling and optimization across frontend (Core Web Vitals, code splitting, lazy loading), backend (N+1 queries, async), and database (EXPLAIN ANALYZE, indexing) layers. Use when the user reports slow code, latency, memory leaks, needs to benchmark, or wants to speed up an application. Measure…