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.
git 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/commands/asfbay-bit/opchain-skills/oc-bugcheck)<a href="https://agentmods.dev/commands/asfbay-bit/opchain-skills/oc-bugcheck"><img src="https://agentmods.dev/badge/commands/asfbay-bit/opchain-skills/oc-bugcheck.svg" alt="Measured on agentmods" 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.00020 | $0.00146 |
| Opus 5 | $0.00010 | $0.00073 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
oc-bugcheck 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 7d 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.
What it actually says
Invoke the oc-bug-check skill and run /oc-bugcheck run on the staged changes.
When it finishes, write .checkpoints/oc-bug-check.checkpoint.json with
skill_state.last_run_verdict set to PASS, FAIL, or UNSUPPORTED, and
skill_state.verified_tree set to the output of git write-tree. The commit
gate reads both: a verdict without a matching tree hash is not evidence that
this code was checked.
UNSUPPORTED is not a pass. If the stack was not recognized, say so plainly.
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.
- 7d ago First seen · 14 lines · 20 tokens per session scan A 8fddbe827252
oc-bugcheck is a command published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 146 once invoked, about $0.0001 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 commands, from other repositories
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.