okf-mcp: Skill for Codex

.agents/skills/okf-v02-migration/SKILL.md

okf-v02-migration is a skill for Codex from doctormacky/okf-mcp. It costs 75 tokens per session (713 once invoked), scanned A, a copy of okf-v02-migration, MIT.

A guided checker for moving Open Knowledge Format (OKF) catalog data from version 0.1 to version 0.2. It creates proposals for review instead of changing files automatically.

In plain words
What is it for?
Checking migration readiness, recording blockers, and creating reviewable mappings and proposals for an OKF catalog.
Why use it?
It helps find migration blockers such as missing authors, citation errors, unsafe paths, and conflicting IDs before changes are proposed.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is doctormacky/okf-mcp's own configuration. It tells Codex how to work on okf-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything okf-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to doctormacky/okf-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/doctormacky/okf-mcp/main/.agents/skills/okf-v02-migration/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/doctormacky/okf-mcp

Made for: Codex.

Wrote 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.

agentmods badge for okf-v02-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/doctormacky/okf-mcp/okf-v02-migration/github.svg)](https://agentmods.dev/skills/doctormacky/okf-mcp/okf-v02-migration)
Your own site
<a href="https://agentmods.dev/skills/doctormacky/okf-mcp/okf-v02-migration"><img src="https://agentmods.dev/badge/skills/doctormacky/okf-mcp/okf-v02-migration/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.

agentmods 80×15 button for okf-v02-migration

Your own site · 80×15
<a href="https://agentmods.dev/skills/doctormacky/okf-mcp/okf-v02-migration"><img src="https://agentmods.dev/badge/skills/doctormacky/okf-mcp/okf-v02-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 713 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.00713
Opus 5 $0.00037 $0.00357
Sonnet 5 $0.00015 $0.00143
Haiku 4.5 $0.00007 $0.00071

Measured 9d ago against content hash b42acc2bc91e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

okf-v02-migration 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 9d 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.

Origin

This is a copy

91% identical to okf-v02-migration — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/okf-v02-migration/SKILL.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OKF v0.2 Migration

Use the package's deterministic migration checker and proposal tools. Never rewrite catalog files directly, invent provenance or verification claims, accept proposals automatically, or mutate a remote bundle.

Workflow

  1. Confirm the repository worktree state before creating proposals. Preserve unrelated changes and stop if migration targets overlap unreviewed edits.
  2. Run okf --root <catalog> migrate check. In an optional multi-root project, run okf --project <config> migrate check <bundle>. Record the classification, blockers, identity collisions, generated-file skips, referenced assets, and migration readiness.
  3. Resolve blockers before proposing anything:
    • Ask the catalog owner for a truthful generated.by actor for every legacy timestamp; require an explicit confirmed mapping.
    • Route generated files back to their generator instead of proposing direct edits.
    • Resolve malformed citations, conformance errors, unsafe paths, and ID or alias collisions without guessing.
    • Supply mappings as {"<concept-uri-or-path>":{"by":"<actor>","confirmed":true}}; $default may be used only after the owner confirms that one actor truthfully applies to every reported timestamp.
    • Use human:<id>, process:<id>, or <provider>/<model> actor syntax. The checker rejects an omitted or non-boolean confirmation.
  4. Run okf --root <catalog> migrate preview '<actor-mappings-json>', or supply the bundle id in multi-root project mode. Review every per-file change against field-mapping.md.
  5. Present the preview and wait for explicit approval before calling okf_propose_v02_migration. That MCP tool requires a writable local root and --authoring; there is intentionally no CLI command that creates proposals.
  6. The proposal tool may create a migration manifest and individual child proposals only. Do not accept any child unless the user explicitly approves that proposal.
  7. Accept the reserved index.md version proposal only after every Stage-A concept proposal is accepted and the whole bundle validates.
  8. Run project validation again and report local evidence, retained legacy fields, remaining generator work, and any external or remote state not verified.

Read the full file on GitHub · 38 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 38 lines · 75 tokens per session scan A b42acc2bc91e

Subscribe to this mod's changes

okf-v02-migration is a skill published in the GitHub repository doctormacky/okf-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 75 tokens to every session and 713 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to okf-v02-migration, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens