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-repo-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-repo-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-repo-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-repo-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-repo-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-repo-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.00111 | $0.01495 |
| Opus 5 | $0.00056 | $0.00747 |
| Sonnet 5 | $0.00022 | $0.00299 |
| Haiku 4.5 | $0.00011 | $0.00150 |
Grade A, and why
oc-repo-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 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Repo Ops is the repository-level cleanliness gate. It does not write the docs packet itself; Docs Forge does that. Repo Ops verifies that the packet exists, that repo state is clean enough to review, and that generated/catalog/source surfaces agree before Git Ops opens a PR.
Command Reference
REPO OPS COMMANDS
/oc-repo Show this menu
/oc-repo audit Read-only repo hygiene sweep
/oc-repo verify PR readiness gate, blocks on failures
/oc-repo clean Apply safe cleanup fixes
/oc-repo catalog Verify catalog, README, registry, package parity
/oc-repo status Show last gate verdict
/checkpoint Show oc-repo-ops checkpoint
Every-PR Gate
oc-git-ops must invoke Repo Ops before creating every PR. The required order is:
- Docs Forge generates or verifies the PR documentation packet.
- Repo Ops verifies repository cleanliness and docs packet presence.
- Bug Check runs the fast code gate before commit.
- Git Ops opens the PR only after Repo Ops and Bug Check pass.
Read references/pr-readiness-gate.md before /oc-repo verify.
/oc-repo audit
Read-only sweep. Report findings without editing files.
Checks:
- Git status, branch, base branch, untracked files, and ignored generated junk.
.gitignorepolicy against the project convention.- Generated artifacts that are missing, stale, or checked in incorrectly.
- Catalog parity: source directories, README tables, registry flags, site catalog, MCP catalog, packaged plugin/cache where configured.
- Documentation parity: Docs Forge checkpoint, PR body fragment, README/product docs, changelog/ADR expectations.
- Checkpoint consistency: stale pointers, generated files that no longer exist, contradictory checkpoint-vs-git state.
- Large/binary artifacts, local logs, temp files, screenshots, and accidental secrets that should not be in the PR.
What ships with it
3 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.
- 7d ago Changed b2b41cfc8d45
- 11d ago First seen · 178 lines · 111 tokens per session scan A baa48de56fe4
oc-repo-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 111 tokens to every session and 1,495 once invoked, about $0.0006 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…