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-migration-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-migration-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-migration-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-migration-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-migration-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-migration-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.00239 | $0.08090 |
| Opus 5 | $0.00120 | $0.04045 |
| Sonnet 5 | $0.00048 | $0.01618 |
| Haiku 4.5 | $0.00024 | $0.00809 |
Grade A, and why
oc-migration-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 6d 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 — 834 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
The "change the engine mid-flight" skill. Fills the gap between oc-reverse-spec ("what I have") and oc-app-architect ("what I want") when the answer is "transform one into the other" — without downtime, without data loss, and with a rollback at every step.
This is inherently multi-session work. A database migration plan might span 3–4 conversations. Checkpoint protocol adoption is critical from day one.
/oc-migrate — Command Reference
MIGRATION OPS COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PLAN
/oc-migrate Show this menu
/oc-migrate assess Inventory current state + classify migration type
/oc-migrate plan Generate incremental migration plan with rollback points
/oc-migrate impact Blast radius analysis — what breaks during each step
EXECUTE
/oc-migrate execute Start or resume execution from migration plan
/oc-migrate step [N] Execute a specific step (with pre/post verification)
/oc-migrate verify Run verification suite against current state
/oc-migrate rollback Revert to last verified checkpoint
OBSERVE
/oc-migrate status Current migration state from checkpoint
/oc-migrate diff Compare current state vs. target state
/oc-migrate history Show completed steps with pass/fail and timing
UTILITIES
/oc-migrate dry-run Simulate the next step without applying changes
/oc-migrate ecosystem Bulk-update opchain skills (format, protocol, oc-orchestrator)
/oc-migrate abandon Abandon an in-progress migration (archive checkpoint)
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command, or describe what you want to migrate.
How This Skill Fits the Pipeline
EXISTING SYSTEM (documented or not)
│
├──► oc-reverse-spec (if undocumented → produces baseline specs)
│
▼
┌──────────────┐
│ MIGRATION-OPS│ current state → migration plan → incremental execution → target state
│ │ Reads: oc-reverse-spec, oc-stack-forge, oc-app-architect, oc-code-auditor
│ │ Chains to: oc-code-auditor (post-migration verify), oc-deploy-ops (cutover)
└──────┬───────┘
│
├──► oc-code-auditor /oc-audit (post-migration quality gate)
├──► oc-deploy-ops /oc-deploy (cutover deployment)
└──► oc-app-architect (if migration reveals spec updates needed)
What ships with it
4 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.
- 6d ago Changed · +3 lines a619b9610903
- 10d ago First seen · 831 lines · 239 tokens per session scan A dff07951791a
oc-migration-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 239 tokens to every session and 8,090 once invoked, about $0.0012 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…