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 agentmods add skills/serradura/okf/skillnpx skills add serradura/okf --skill skillgit clone --depth 1 https://github.com/serradura/okfWrote 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/serradura/okf/skill)<a href="https://agentmods.dev/skills/serradura/okf/skill"><img src="https://agentmods.dev/badge/skills/serradura/okf/skill.svg" alt="Measured on agentmods" 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 | $0.00183 | $0.03188 |
| Opus 5 | $0.00092 | $0.01594 |
| Sonnet 5 | $0.00037 | $0.00638 |
| Haiku 4.5 | $0.00018 | $0.00319 |
Grade A, and why
okf 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- okf — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Knowledge Format (OKF)
You are the OKF expert in this repository. OKF is knowledge as code: a
directory of markdown files, each with YAML frontmatter, that both humans and
agents read from the same source. It is minimal on purpose — no schema registry,
no runtime, no SDK. All the power lives in conventions and judgment, not in
enforcement. This skill is where that judgment lives; the okf CLI handles the
mechanics.
Two ideas govern everything:
- Dual audience. Every file must serve a human skimming it and an agent extracting from it. That is why bodies are structural markdown and links are plain markdown links — both readers already understand them.
- The graph is emergent. Files are nodes, markdown links are edges. You never declare a graph; it arises from how you link concepts. Good linking is good knowledge modelling.
The hard rules (§11 conformance)
Three conditions, all hard — validate fails a bundle on any of them:
- §11 cond. 1 every non-reserved
.mdfile has a parseable YAML frontmatter block; - §11 cond. 2 every such block has a non-empty
type; - §11 cond. 3 every reserved file present is well-formed — a nested
index.mdhas no frontmatter, the bundle-rootindex.mdcarries onlyokf_version, andlog.mddate headings are ISOYYYY-MM-DD.
Everything else is soft guidance, and consumers MUST tolerate missing optional fields, unknown types, and broken links — a bundle is never rejected over them.
Three lenses — hold them separate
Judging a bundle means asking three different questions. Conflating them is the most common mistake:
| Lens | Question | Tool | Nature |
|---|---|---|---|
| Legal | Is it conformant OKF? (§11) | validate |
Binary, tolerant |
| Good | Is it navigable, complete, fresh? | lint |
Advisory, structural |
| True | Is it consistent and current? | you, over lint --json |
Semantic — needs meaning |
What ships with it
26 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.
- playbooks/consume.md 1.1 KB
- playbooks/curate.md 2.2 KB
- playbooks/doctor.md 2.7 KB
- playbooks/maintain.md 5.0 KB
- playbooks/menu.md 3.1 KB
- playbooks/migrate.md 3.9 KB
- playbooks/produce.md 2.0 KB
- playbooks/refine.md 8.1 KB
- playbooks/search.md 5.7 KB
- reference/APACHE-2.0.txt 11 KB
- reference/authoring.md 16 KB
- reference/cli.md 8.9 KB
- reference/cli/checks.md 10 KB
- reference/cli/graph.md 3.2 KB
- reference/cli/map.md 5.8 KB
- reference/cli/registry.md 7.8 KB
- reference/cli/search.md 8.8 KB
- reference/cli/serve.md 5.1 KB
- reference/cli/views.md 3.9 KB
- reference/spec-map.md 2.4 KB
- reference/SPEC.md 37 KB
- templates/attested-computation.md 1.5 KB
- templates/concept.md 1.2 KB
- templates/index.md 254 B
- templates/log.md 255 B
- templates/root-index.md 282 B
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.
- 4d ago First seen · 201 lines · 183 tokens per session scan A 800bf9a74850
okf is a skill published in the GitHub repository serradura/okf (142 stars, last pushed 9d ago), licensed Apache-2.0. It adds 183 tokens to every session and 3,188 once invoked, about $0.0009 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-30.
Other skills, from other repositories
kb-ingest
Ingest a source into the knowledge bundle. Use when the user wants to capture, ingest, file, process, or "add this" — a note, transcript, email, PDF, image, web page, or any raw source — into a knowledge/ bundle, or drops content for processing. Reads the source once, extracts its signal, and integrates it across the…
kb-query
Answer from the knowledge bundle. Use when the user asks what they/the project know about something, wants to look something up, explore connections, or compare things that live in a knowledge/ bundle — and when any task would be informed by an existing bundle, consult it here before answering from scratch. Navigates…
kb
Portable OKF knowledge bundle for coding-agent memory and LLM wikis. Use when the user wants to start a wiki, ingest a source, document a repository, query project knowledge with citations, lint for drift, or visualize connections; whenever a repo has a knowledge/ bundle that should inform the task; and when another…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…