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-monitoring-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-monitoring-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-monitoring-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-monitoring-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-monitoring-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-monitoring-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.00143 | $0.07903 |
| Opus 5 | $0.00072 | $0.03952 |
| Sonnet 5 | $0.00029 | $0.01581 |
| Haiku 4.5 | $0.00014 | $0.00790 |
Grade A, and why
oc-monitoring-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 8d 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 — 753 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Post-deployment observability skill. Deploy-ops ships the code; oc-monitoring-ops watches it run. Covers five domains: uptime monitoring, error tracking, structured logging, alerting pipelines, and incident response.
This skill does NOT build features or deploy code — it instruments what's already deployed and establishes the feedback loop that catches problems before users report them.
/oc-monitor — Command Reference
MONITORING OPS COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SETUP
/oc-monitor setup Guided observability stack setup for a project
/oc-monitor stack Recommend monitoring tools for the stack
/oc-monitor instrument Add structured logging + error capture to codebase
OBSERVE
/oc-monitor health Live health check — hit endpoints, report status
/oc-monitor errors Check error tracking service for recent issues
/oc-monitor uptime Show uptime status and recent incidents
/oc-monitor metrics Key metrics snapshot (latency, error rate, throughput)
/oc-monitor status Current monitoring state from checkpoint
ALERT
/oc-monitor alerts Design or audit alerting rules
/oc-monitor oncall Set up on-call rotation and escalation
/oc-monitor slo Define or review SLOs/SLIs/error budgets
RESPOND
/oc-monitor incident Start or review an incident response
/oc-monitor runbook Generate or update operational runbooks
/oc-monitor postmortem Structured post-incident review
REPORT
/oc-monitor dashboard Design an ops monitoring dashboard (routes to oc-dash-forge)
/oc-monitor report Generate weekly/monthly ops report
/oc-monitor audit Full observability maturity assessment
/oc-monitor compare Compare two monitoring snapshots (drift detection)
SESSION
/checkpoint Show checkpoint status
/checkpoint show Display full checkpoint JSON
/checkpoint reset Archive and restart
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-monitor to see this again.
What ships with it
7 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.
- 8d ago Changed · +2 lines 86422b4a4a56
- 11d ago First seen · 751 lines · 143 tokens per session scan A a0282413cd5c
oc-monitoring-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 143 tokens to every session and 7,903 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…