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-code-auditorgit 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-code-auditor)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-code-auditor"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-code-auditor.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.00060 | $0.05213 |
| Opus 5 | $0.00030 | $0.02606 |
| Sonnet 5 | $0.00012 | $0.01043 |
| Haiku 4.5 | $0.00006 | $0.00521 |
Grade B, and why
oc-code-auditor scanned grade B with 2 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 4d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| Destructive op (`DROP`/`DELETE`/`rm -rf`) built from tool/user input | AI-TOOL-005 | CRITICAL | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| Shell exec (`exec`/`spawn`/`child_process`/`subprocess`, `shell: true`) reachable from a tool | AI-TOOL-002/003 | CRITICAL | How it starts
The opening of the file, as written. The whole thing — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Auditor
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Tri-agent code quality system: Auditor finds problems → Fixer proposes remediations → Verifier confirms the fixes actually solve the findings (not just cosmetic reshuffles).
The Auditor-only mode (/oc-audit) runs a one-pass sweep and produces a findings report.
The full harness (/oc-audit fix-all) chains all three agents for find → fix → verify.
/oc-audit — Command Reference
CODE AUDITOR COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SWEEP MODES
/oc-audit full Full codebase sweep — all categories
/oc-audit security Security-focused (auth, injection, secrets, CORS)
/oc-audit perf Performance (N+1, bundle, caching, queries)
/oc-audit quality Code quality (dead code, complexity, patterns)
/oc-audit ux UX/accessibility (a11y, states, consistency, responsive)
/oc-audit pre-deploy Pre-deployment gate (security + perf + config)
/oc-audit file [path] Audit specific file(s)
/oc-audit diff Audit git diff or staged changes
TRI-AGENT HARNESS
/oc-audit fix-all Run full Auditor → Fixer → Verifier loop
/oc-audit fix <id> Fix a single finding with verification
/oc-audit verify Re-run Verifier on previous fixes
BOOTSTRAP
/oc-audit test-bootstrap Generate test suite for untested codebase
UTILITIES
/oc-audit report Regenerate findings report from last audit
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-audit to see this again.
Tri-Agent Architecture
CODEBASE
│
▼
┌──────────┐
│ AUDITOR │ Sweeps for problems
│ │ Output: findings report with severity + location
└────┬─────┘
│
▼ (findings)
┌──────────┐
│ FIXER │ Proposes concrete code changes per finding
│ │ Output: diffs/patches per finding
└────┬─────┘
│
▼ (fixes)
┌──────────┐
│ VERIFIER │ Confirms each fix addresses the finding
│ │ Cannot see Fixer's reasoning — only the diff and original finding
│ │ Output: verified/rejected per fix
└──────────┘
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.
- 4d ago Changed · +5 lines 191fe96bb441
- 7d ago First seen · 540 lines · 60 tokens per session scan B 3ccd85958be3
oc-code-auditor is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 60 tokens to every session and 5,213 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.