What is oc-bug-check?

A fast quality gate that checks changed code before it is committed to version control. It checks types, lint rules, tests, common bad patterns, exposed secrets, the build, and vulnerable dependencies.

Use it before committing changes, run it on a whole codebase, apply fixable formatting or lint changes, and block a commit when a required check fails.

It catches common problems before they enter the project's history, while reporting failures separately from non-blocking warnings.

oc-bug-check — Skill for Claude Code by asfbay-bit

Install

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.

Any agent

npx skills add asfbay-bit/opchain-skills --skill oc-bug-check

Clone the repo

git clone --depth 1 https://github.com/asfbay-bit/opchain-skills

Made for: Claude Code.

Or install opchain, the plugin that ships this one along with the rest of its 33 skills, 12 commands, 3 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-bug-check/github.svg)](https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-bug-check)

Your own site

<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-bug-check"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-bug-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-bug-check"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-bug-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,079 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00135	$0.07079
Opus 5	$0.00068	$0.03540
Sonnet 5	$0.00027	$0.01416
Haiku 4.5	$0.00014	$0.00708

Measured 6d ago against content hash fcbe516b19af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

oc-bug-check 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.

plugins/opchain/skills/oc-bug-check/SKILL.md · 764 lines

How it starts

The opening of the file, as written. The whole thing — 764 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bug Check

On first invocation, read references/orchestrator.md and follow its welcome protocol.

Fast pre-commit QA gate. Runs in under 2 minutes. Catches the bugs, type errors, test failures, and anti-patterns that shouldn't make it into a commit — before they cost real debugging time downstream.

This is NOT oc-code-auditor. Code-auditor runs a deep tri-agent sweep (Auditor → Fixer → Verifier) that takes 30+ minutes and produces a graded report. Bug-check is the metal detector at the door — fast, blunt, binary: every check resolves to PASS or FAIL. Individual checks may emit advisory WARN notes (e.g. "no test suite detected") that are surfaced in the report but do not affect the gate verdict — only FAIL blocks the commit.

/oc-bugcheck — Command Reference

BUG CHECK COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  GATE
  /oc-bugcheck              Run all checks on staged/changed files
  /oc-bugcheck run          Same as /oc-bugcheck
  /oc-bugcheck run --all    Run on entire codebase (not just changes)
  /oc-bugcheck fix          Auto-fix what's fixable (lint, formatting)

  CONFIG
  /oc-bugcheck config       Show or edit check configuration
  /oc-bugcheck config strict    Enable strict mode (zero warnings allowed)
  /oc-bugcheck config lenient   Allow warnings, block only on errors

  REPORT
  /oc-bugcheck report       Show last run results from checkpoint
  /oc-bugcheck history      Show pass/fail trend from checkpoint

  OVERRIDE
  /oc-bugcheck bypass       Skip gate this once (logs the bypass in checkpoint)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Runs automatically before /oc-git-commit and /oc-git-sync.

Session Persistence (Checkpoint Protocol)

Checkpoint: {project-dir}/.checkpoints/oc-bug-check.checkpoint.json

Resume on Start

When /oc-bugcheck is invoked:

Check for checkpoint
If exists: show last verdict, streak, carried debt count
If carried debt > 0: surface bypassed issues before running new checks
Run the check suite (no "continue/restart" prompt — oc-bug-check always runs fresh)

Read the full file on GitHub · 764 lines

Files

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.

Changes

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 · +12 lines fcbe516b19af
9d ago First seen · 752 lines · 135 tokens per session scan A 2175ce92dd92

Subscribe to this mod's changes

oc-bug-check is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 135 tokens to every session and 7,079 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.

Security Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

oc-bug-check