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 instructions/umairbaig8/okf-generator/copilot-instructionsgit clone --depth 1 https://github.com/UmairBaig8/okf-generatorWrote 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/instructions/umairbaig8/okf-generator/copilot-instructions)<a href="https://agentmods.dev/instructions/umairbaig8/okf-generator/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/umairbaig8/okf-generator/copilot-instructions.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.1 | $0.00481 | $0.00481 |
| Opus 5 | $0.00241 | $0.00241 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
okf-generator copilot-instructions.md 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.
What it actually says
OKF Knowledge Bundle — Copilot Instructions
CRITICAL RULE: Never read source files directly for context
This project uses okf-generator to produce an OKF v0.2 knowledge bundle at ./okf_bundle/. The bundle contains structured markdown files — one per function, class, module, and dependency.
BEFORE reading or editing any source file, you MUST run:
okf lookup --bundle ./okf_bundle <ConceptName>
This returns signature, parameters, docstring, dependencies, callers, and callees in milliseconds — faster and more accurate than reading the source file.
Common lookups
# Single concept full detail
okf lookup --bundle ./okf_bundle ClassName
# All concepts from one source file
okf lookup --bundle ./okf_bundle --file path/to/source.py
# Filter by type
okf lookup --bundle ./okf_bundle --type Class
okf lookup --bundle ./okf_bundle --type Function
okf lookup --bundle ./okf_bundle --type Dependency
# Filter by language
okf lookup --bundle ./okf_bundle --tag lang:python
okf lookup --bundle ./okf_bundle --tag lang:typescript
okf lookup --bundle ./okf_bundle --tag lang:go
# Filter by ecosystem
okf lookup --bundle ./okf_bundle --tag ecosystem:pip
okf lookup --bundle ./okf_bundle --tag ecosystem:npm
okf lookup --bundle ./okf_bundle --tag ecosystem:cargo
# JSON output for programmatic use
okf lookup --bundle ./okf_bundle --json <Name>
# Dependencies (all or by ecosystem)
okf lookup --bundle ./okf_bundle --type Dependency
okf lookup --bundle ./okf_bundle --type Dependency --tag ecosystem:pip --compact
Seeing what changed between bundles
okf diff ./okf_bundle.bak ./okf_bundle --compact
okf diff ./okf_bundle.bak ./okf_bundle --json
Bundle location
- Default:
./okf_bundle/ - Also checked:
./Knowlege/okf_bundle/,./knowledge/okf_bundle/ - okf-generator README
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 First seen · 59 lines · 481 tokens per session scan A 5af289a9f016
okf-generator copilot-instructions.md is an instructions file published in the GitHub repository UmairBaig8/okf-generator (101 stars, last pushed 1mo ago), licensed MIT. It adds 481 tokens to every session, about $0.0024 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).