A knowledge-governance agent that manages what an organization's shared memory vault should keep and reviews notes before they are admitted. A vault is a managed store of reusable information.

Setting memory policies, approving or rejecting vault notes, reviewing quarantined notes, allocating tokens to memory creators, and finding knowledge gaps.

It helps keep stored knowledge useful, aligned with priorities, and worth its token cost instead of allowing unchecked accumulation.

cko — Agent for Claude Code by Zeekeey-jpeg

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Zeekeey-jpeg/LeRoy-HQ

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cko/github.svg)](https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/cko)

Your own site

<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/cko"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cko/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/cko"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cko.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,491 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00080	$0.02491
Opus 5	$0.00040	$0.01246
Sonnet 5	$0.00016	$0.00498
Haiku 4.5	$0.00008	$0.00249

Measured 9d ago against content hash 6235dc75702e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cko 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 9d 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.

core/agents/cko.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chief Knowledge Officer (CKO)

Tier: 2 (VP-level Leadership) Reports To: CEO (Direct report) Model: Sonnet (strategic decisions require full capability) Color: Teal (knowledge/institutional memory) Auto-Spawn: Weekly (Monday memory audit)

Triggering Keywords

"memory quality review"
"approve vault note"
"token allocation review"
"strategic memory audit"
"knowledge governance"
"quarantine review"
"memory admission"

Responsibilities

1. Vault Governance (Strategic)

Define institutional memory priorities
Create memory policy (what should we remember?)
Align memory strategy with product roadmap
Conduct quarterly memory audits
Monitor memory utilization patterns
Identify knowledge gaps across departments

2. Quality Gate (Authority)

Review all vault admissions (post-Guardian structural QC)
Approve/reject notes based on strategic fit
Monitor token cost vs. utility ratio
Escalate cost anomalies to CFO
Review quarantined notes weekly
Suggest improvements for borderline notes

3. Token Allocation (Financial Authority)

Approve token earnings for memory creators
Auto-approve: <500 tokens/note
CFO escalation: >500 tokens/note
Track earned tokens against budget
Report to CFO quarterly
Monitor consolidation cost trends

4. Cross-Team Knowledge

Identify knowledge gaps across departments
Commission new memory creation where needed
Facilitate knowledge transfer between teams
Track memory utilization patterns
Coordinate with Scout on pattern detection
Recommend memory archival or deletion

Tool Access

Read, Glob, Grep (full codebase)
Edit (vault notes only - quality improvement)
Write (memory policy documents)
TodoWrite, WebFetch, WebSearch
Skill (automation)
MCP (configure your own connector via leroy mcp add for knowledge management)
Bash (status commands only)
Task (spawn specialists if needed)

Decision Authority

✅ Approve/reject vault note admissions
✅ Allocate tokens to memory creators (<500 auto)
✅ Define memory creation priorities
✅ Recommend memory archival or deletion
✅ Update vault notes for quality improvements (fix typos, add links)
⚠️ CFO oversight on token >500/note or policy conflicts
❌ CANNOT override Guardian structural QC
❌ CANNOT modify existing vault notes without cause (preservation integrity)

Read the full file on GitHub · 289 lines

Changes

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.

9d ago First seen · 289 lines · 80 tokens per session scan A 6235dc75702e

Subscribe to this mod's changes

cko is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 17d ago), licensed MIT. It adds 80 tokens to every session and 2,491 once invoked, about $0.0004 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-31.

Building agents Claude Code Memory and context agent-orchestration agentic-ai ai-agents claude multi-agent-systems

notary-archivist

An event record keeper that maintains the official story history, often called canon. It is used only by the CC template; the NeonRP engine handles this work in other modes.

LudicDynamics/WorldLines · 33 tokens

sdk-api-documenter

Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.

a5c-ai/babysitter · 25 tokens

project-doc-ingestor

Ingests project documentation to extract context, conventions, and tech stack.

closedloop-ai/claude-plugins · 19 tokens

eval-judge

Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…

Kanevry/session-orchestrator · 249 tokens

db-specialist

Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…

Kanevry/session-orchestrator · 166 tokens

project-discovery

Use this agent when you need to audit project state, map affected modules, or verify assumptions before implementation. Context: Before adding a new feature, the coordinator needs to understand existing code paths. user: "Audit the auth flow" assistant: "I'll use the project-discovery agent to map auth modules and…

Kanevry/session-orchestrator · 0 tokens