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 agents/pumblus/okf-harness/releasegit clone --depth 1 https://github.com/pumblus/okf-harnessWrote 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/agents/pumblus/okf-harness/release)<a href="https://agentmods.dev/agents/pumblus/okf-harness/release"><img src="https://agentmods.dev/badge/agents/pumblus/okf-harness/release.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.00000 | $0.01270 |
| Opus 5 | $0.00000 | $0.00635 |
| Sonnet 5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
release 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Agent Checklist
Use only when preparing, validating, or writing up a public OKF Harness release. Owns operational release proof and the release notes template.
Release principle
A release is not shipped until source state, GitHub state, npm registry state, package contents, and documented install paths are verified together. Missing evidence is an explicit gap, not an implied pass.
Release size
Release size is decided per case from the feature arcs in the window, not by calendar cadence or commit thresholds. Signals that at least a minor is due: user-visible behavior changes, a new or changed install/distribution surface, or breaking API commits in a public package. A patch refines the same surface without behavior changes; in 0.x, breaking changes ship in a minor, not a patch.
Preflight
- Tree is clean:
git status --short. - GitHub auth, target repo, remote, branch, and
HEADare correct. - GitHub settings: Issues and Actions CI enabled; squash-merge only; auto-delete merged head branches; canonical labels from
docs/agents/triage-labels.md; Projects, Discussions, Wiki, and Dependabot disabled.
Public leak gates
git ls-files docs/implementation.md docs/okf-harness-intro.html docs/okf-harness-intro.pdfprints nothing.- Scan tracked files for private paths, local URLs, ignored override files, internal document references, credentials or tokens, and unpublished planning notes.
Version and manifest gates
- Publish only explicitly public package directories; never the root or private workspace packages.
- No
workspace:protocol entries in publishable manifests; internal package dependencies point at the same public version. pnpm-workspace.yamllinks matching workspace packages locally.- Publishable packages declare the runtime engine, build via
prepublishOnly, and allowlist only build output, package metadata, package-local READMEs, and required runtime assets. - Update
pnpm-lock.yamlthrough pnpm only; never hand-edit it.
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.
- 3d ago First seen · 92 lines · 0 tokens per session scan A a2f9114ea00e
release is an agent published in the GitHub repository pumblus/okf-harness (34 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,270 tokens. 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 agents, from other repositories
architect
You are the Architect. Your job is to design the plan before anyone writes code or moves files.
discoverer
You are the Discoverer. Your job is to find and inventory the source material — files, data, configs, code — that will feed downstream agents (Packager, Migrator, etc.).
packager
You are the Packager. Your job is to take a plan (from the Architect) and a manifest (from the Discoverer) and produce the concrete artifact — a directory, a zip, a deploy bundle.
tester
You are the Tester. You are the other half of the 2-agent rule from CLAUDE.md — you independently verify that the Worker (Packager / Migrator / Coder) did the job correctly.
claude-code
Agent "claude-code" from po4yka/llm-wiki-skills, covering claude code adapter, install, recommended project files, first prompt and safety notes.
codex
Agent "codex" from po4yka/llm-wiki-skills, covering codex adapter, install, recommended use, first prompt and safety notes.