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-docs-forgegit 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-docs-forge)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-docs-forge"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-docs-forge/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-docs-forge"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-docs-forge.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.00108 | $0.01821 |
| Opus 5 | $0.00054 | $0.00911 |
| Sonnet 5 | $0.00022 | $0.00364 |
| Haiku 4.5 | $0.00011 | $0.00182 |
Grade A, and why
oc-docs-forge 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Forge
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Docs Forge turns a code change into the documentation that must travel with it. It owns the content, wording, placement, and freshness checks for PR bodies, PR comments, README/catalog docs, product docs, ADRs, changelog notes, and linked ticket summaries.
Boundary: Docs Forge writes and verifies documentation. Repo Ops decides whether the repository is clean enough to open the PR. Git Ops creates the branch, commit, push, and PR after these gates pass.
Command Reference
DOCS FORGE COMMANDS
/oc-docs Show this menu
/oc-docs pr Generate the PR documentation packet
/oc-docs readme Refresh README/catalog docs affected by this change
/oc-docs standardize Normalize docs frontmatter, headings, owners, links
/oc-docs upkeep Run freshness and drift review across docs
/oc-docs verify Verify the PR docs packet is present and current
/checkpoint Show oc-docs-forge checkpoint
Every-PR Contract
Every PR must contain Docs Forge output in at least one visible surface:
- The PR body, for normal documentation packets.
- A PR comment with marker
<!-- opchain:oc-docs-forge:pr-docs -->, when the documentation packet is too long for the body. - Both the body and a comment, when the body needs a compact summary and the comment carries migration notes, screenshots, large tables, or generated docs.
The PR body must always include a ## Documentation section. If no user-facing
documentation changed, say so explicitly and explain why. Silence is not a pass.
Read references/pr-documentation-packet.md before generating or verifying PR
documentation.
/oc-docs pr
Inputs:
git diff --statand changed file list.- Commit log against the base branch, when available.
- Relevant checkpoints from oc-app-architect, oc-reverse-spec, oc-code-auditor, oc-bug-check, oc-release-ops, oc-api-dev, oc-stack-forge, and oc-repo-ops.
- Existing README, docs, ADRs, changelog, API docs, product docs, and catalog pages touched by the change.
- Linked ticket or PR draft context, when oc-git-ops provides it.
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.
- 5d ago Changed 49d33ecf2a11
- 8d ago First seen · 211 lines · 108 tokens per session scan A 90b7ae619aa5
oc-docs-forge is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 108 tokens to every session and 1,821 once invoked, about $0.0005 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.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.