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 asfbay-bit/opchain-skills --skill oc-telemetry-opsgit clone --depth 1 https://github.com/asfbay-bit/opchain-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/asfbay-bit/opchain-skills/oc-telemetry-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-telemetry-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-telemetry-ops/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/asfbay-bit/opchain-skills/oc-telemetry-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-telemetry-ops.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.00139 | $0.02354 |
| Opus 5 | $0.00069 | $0.01177 |
| Sonnet 5 | $0.00028 | $0.00471 |
| Haiku 4.5 | $0.00014 | $0.00235 |
Grade A, and why
oc-telemetry-ops 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 6d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telemetry Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Answer "is anyone actually using this, and which parts?" — without betraying
opchain's local-first, no-backend stance. Telemetry Ops meters skill/phase
usage into a local SQLite store (.checkpoints/usage.sqlite), strictly
opt-in, and produces an anonymized aggregate that the public /dashboard renders
as a credibility surface (pipelines run, most-used skill, model-tier mix,
cost-per-shipped-feature). The raw store never leaves the machine; only the
small, aggregated, identity-free rollup is ever published.
This is not a hosted analytics product and not PostHog (that's the site's consent-gated client analytics). Telemetry Ops is about the skills pipeline's own usage, recorded where the work happens — locally, in git-adjacent state — so the numbers are real (they come from actual runs) and private (they stay put unless you export an aggregate).
Default OFF. Presence is not consent. Metering does nothing until
/oc-telemetry enableflips it on. Thetelemetry_handlecheckpoint field existing is not consent;enabled: trueis. Seereferences/privacy-consent.md.
/oc-telemetry — Command Reference
TELEMETRY OPS COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONSENT (default: OFF)
/oc-telemetry enable Opt in — create the local store, set telemetry_handle.enabled
/oc-telemetry disable Opt out — stop metering (store kept locally, your call to delete)
/oc-telemetry status Show consent state, store location, row count;
exits non-zero when enabled with no store
(enabled-with-no-store never reads healthy)
METERING & EXPORT
/oc-telemetry aggregate Roll the local store up into an anonymized summary
/oc-telemetry export Emit the publishable aggregate (no PII) for /dashboard
UTILITIES
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-telemetry to see this again.
What ships with it
5 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.
- 6d ago Changed · +2 lines b405f311312f
- 10d ago First seen · 218 lines · 139 tokens per session scan A c5eeec01e8e4
oc-telemetry-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 139 tokens to every session and 2,354 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…