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 xSAVIKx/okf-skills --skill okf-gitgit clone --depth 1 https://github.com/xSAVIKx/okf-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/xsavikx/okf-skills/okf-git)<a href="https://agentmods.dev/skills/xsavikx/okf-skills/okf-git"><img src="https://agentmods.dev/badge/skills/xsavikx/okf-skills/okf-git/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/xsavikx/okf-skills/okf-git"><img src="https://agentmods.dev/badge/skills/xsavikx/okf-skills/okf-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.00605 |
| Opus 5.5 | $0.00024 | $0.00242 |
| Sonnet 5.5 | $0.00012 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
okf-git 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 21d 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
Skill: okf-git (Git Repository OKF Connector)
This skill produces and ingests OKF bundles documenting Git repository file trees, including revision history metadata (commit times, authors, messages), respecting .gitignore and .okfignore files.
Setup
The connector is written in Go and requires Go 1.24+ to build from source:
# Install the published binary (Go 1.24+) — no clone needed:
go install github.com/xSAVIKx/okf-skills/skills/[email protected]
# …or build from a clone of the repository:
cd skills/okf-git
go build -o okf-git .
Commands
1. produce
Traverses the Git repository files, skips ignored files, queries commit logs for history metadata, reads description comments from .okf-metadata.yaml, and outputs an OKF bundle.
./okf-git produce --repo <repository-path> --out <bundle-output-dir>
Options:
--repo(string): The path to the local Git repository to document (required).--out(string): The path where the generated OKF bundle will be created (required).
2. ingest
Validates an OKF bundle against tracked Git repository files and optionally syncs descriptions back into .okf-metadata.yaml at the repository root.
./okf-git ingest --repo <repository-path> --bundle <okf-bundle-dir> [--sync]
Options:
--repo(string): The path to the local Git repository to update (required).--bundle(string): The path to the OKF bundle to ingest (required).--sync(bool): If true, updates.okf-metadata.yamlat the repository root with the descriptions from the bundle.
3. Inspect the Schema (self-description)
Print a machine-readable JSON description of this skill's commands and flags (used by okf-mcp to expose the skill as an MCP tool):
./okf-git schema
What ships with it
9 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.
- 21d ago Changed 654697ad1112
- 1mo ago First seen · 60 lines · 61 tokens per session scan A f1d8f690f2de
okf-git is a skill published in the GitHub repository xSAVIKx/okf-skills (38 stars, last pushed 22d ago), licensed Apache-2.0. It adds 61 tokens to every session and 605 once invoked, about $0.0002 per session on Opus 5.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
okf-authoring
Author Open Knowledge Format (OKF) bundles — knowledge represented as a directory of markdown files with YAML frontmatter. Use when asked to create, write, generate, enrich, or validate an OKF bundle or OKF concept docs; to turn a data source (Glue database, API, database, catalog), documentation, or a research topic…
report-authoring
The report-authoring methodology: required structure, language, evidence discipline, and figure selection. Read BEFORE your first createreport of a conversation - the tool validates shape; this is everything it cannot check.
okf-open-knowledge-format
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert…
speq-implement-pr
Builds a planned feature on its feat/plan-name branch as a follow-up to /speq-plan-pr: implements, bumps the version, runs the real test suites, records the specs if green, comments the verification, and marks the PR ready. Run again to resume. Arg: plan name, PR number, or branch name.
speq-git-operations
The git/gh operation-to-command mapping and return formats — invoked directly by /speq-plan-pr and /speq-implement-pr.
speq-plan-pr
Plans a feature through the same clarifying interview as /speq-plan, then creates the feat/plan-name branch, commits the plan, and opens a draft pull request. Arg: feature intent text, plan name, PR number, or branch name.