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/cofin/flow/okfnpx skills add cofin/flow --skill okfgit clone --depth 1 https://github.com/cofin/flowWhat 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.00042 | $0.01410 |
| Opus 5 | $0.00021 | $0.00705 |
| Sonnet 5 | $0.00008 | $0.00282 |
| Haiku 4.5 | $0.00004 | $0.00141 |
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 2d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Knowledge Format (OKF)
Author, validate, tag, and structure Open Knowledge Format (OKF v0.2) knowledge bundles and hierarchical concept documents.
Materialization Contract
default_scaffold:
- bundles/index.md
- bundles/log.md
- bundles/product/product.md
- bundles/product/tech-stack.md
- bundles/knowledge/index.md
- bundles/knowledge/workflow.md
repository_evidence:
applies_to: [architecture, data-model, domain, pattern, standard]
required: [repository_relative_paths, symbols_or_observed_behavior]
decision_evidence:
applies_to: [decision, rejected-alternative]
required: [explicit_user_decision, recorded_at, actor]
path_policy:
shape: repository_derived_hierarchy
nested_paths: preserve
unknown_types: tolerate
rerun: idempotent_without_duplicate_or_overwrite
links: resolve_before_commit
tags:
optional_by_okf: true
required_by_profile: non_empty_lowercase_hyphenated_strings
empty_list_satisfies_required: false
archive:
resident_spec_directories: forbidden
effect: knowledge_synthesis_log_append_and_completed_spec_removal
Setup creates only the default scaffold. Do not pre-create optional namespace directories. Materialize architecture, data-model, domain, pattern, or standard chapters only after inspecting named repository-relative paths and recording the symbols or observed behavior that support each fact. Materialize a decision only from a recorded explicit user decision with its actor and timestamp; record rejected alternatives inside that decision rather than in a separate rejections tree. A placeholder, inferred layering convention, sample schema, invented glossary term, or sample ADR is not evidence.
Materialize reusable conventions at knowledge/patterns/<topic>.md only from
the same repository evidence. Continue to tolerate an existing legacy
knowledge/patterns.md, but do not create or advertise that catch-all path.
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.
- 2d ago First seen · 151 lines · 42 tokens per session scan A 7672f647be6f
okf is a skill published in the GitHub repository cofin/flow (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,410 once invoked, about $0.0002 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
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.