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-security-hardeninggit 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-security-hardening)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-security-hardening"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-security-hardening/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-security-hardening"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-security-hardening.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.00237 | $0.03832 |
| Opus 5.5 | $0.00095 | $0.01533 |
| Sonnet 5.5 | $0.00047 | $0.00766 |
| Haiku 4.5 | $0.00024 | $0.00383 |
Grade A, and why
oc-security-hardening 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 26d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Hardening
On first invocation, read references/orchestrator.md and follow its welcome protocol.
The execution half of opchain's security pair. oc-security-auditor answers "where are we exposed?" — STRIDE, OWASP mapping, posture scores. This skill answers "then close it, and prove it stays closed": it turns findings into merged config and code, records every applied control in a manifest, and wires the gate that re-verifies the manifest before every deploy.
The verb pair, so nobody trips on it: /oc-hardening (auditor) audits
the hardening posture. /oc-harden (this skill) does the hardening.
Not an offensive tool: this skill never runs exploits, scanners, or penetration tests against any target, its own included — verification is limited to reading the repo's config, running the project's own test suite, and fetching response headers from the project's own deploy targets. External pen-test reports are consumed as findings to fix, never reproduced.
Command Reference
SECURITY HARDENING COMMANDS
/oc-harden Show this menu
/oc-harden baseline Apply the stack-aware secure baseline
/oc-harden fix Remediate a specific auditor finding
/oc-harden csp Staged CSP rollout: report-only → enforce
/oc-harden gate Install / verify the pre-deploy hardening gate
/oc-harden verify Re-verify manifest controls (all, or one by id)
/oc-harden status Manifest health, unmanaged-control scan, last verify
/checkpoint Show oc-security-hardening checkpoint
The manifest: .opchain/hardening.yaml
Every control this skill applies is recorded with how it verifies (format:
references/hardening-manifest.md):
# excerpt of .opchain/hardening.yaml
controls:
- id: headers.hsts
control: "HSTS max-age=31536000; includeSubDomains"
applied_in: "src/index.js (securityHeaders middleware)"
verify: { method: http, url: "/", header: "Strict-Transport-Security" }
source_finding: "oc-security-auditor 2026-08-22 header sweep (5/8)"
- id: api.rate-limit.mcp
control: "POST /mcp per-IP rate limit + checkpoint TTL"
applied_in: "src/index.js + KV binding"
verify: { method: test, cmd: "npx --no -- vitest run tests/mcp-route.test.js" }
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.
- 26d ago Changed 6e6eed7c39f0
- 29d ago Changed 430092ebc15f
- 1mo ago Changed b8dddb0c42e7
- 1mo ago Changed · +17 lines 754d93dc7413
- 1mo ago First seen · 292 lines · 237 tokens per session scan A a4f7ca5a5df4
oc-security-hardening is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 237 tokens to every session and 3,832 once invoked, about $0.0009 per session on Opus 5.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-09-04.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…