What is knowledge-ops?

A skill for managing a knowledge base across local files, memory tools, vector stores, and Git repositories. It covers adding, organizing, syncing, deduplicating, and searching information.

Use it to save conversations or documents, synchronize knowledge, remove duplicates, and retrieve information about a topic.

It gives projects a structured way to keep knowledge consistent across several storage systems instead of relying on scattered notes.

knowledge-ops — Skill for Claude Code and Codex by Jamkris

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.

Any agent

npx skills add Jamkris/everything-gemini-code --skill knowledge-ops

Clone the repo

git clone --depth 1 https://github.com/Jamkris/everything-gemini-code

Made for: Claude Code, Codex.

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/skills/jamkris/everything-gemini-code/knowledge-ops/github.svg)](https://agentmods.dev/skills/jamkris/everything-gemini-code/knowledge-ops)

Your own site

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/knowledge-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/knowledge-ops/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/skills/jamkris/everything-gemini-code/knowledge-ops"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/knowledge-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,418 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 89% copy Near-identical to another mod 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.00053	$0.01418
Opus 5.5	$0.00021	$0.00567
Sonnet 5.5	$0.00011	$0.00284
Haiku 4.5	$0.00005	$0.00142

Measured 1mo ago against content hash eec2abefab55, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

knowledge-ops 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 1mo 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.

Origin

This is a copy

89% identical to knowledge-ops — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/knowledge-ops/SKILL.md · 155 lines

How it starts

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

Knowledge Operations

Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across multiple stores.

Prefer the live workspace model:

code work lives in the real cloned repos
active execution context lives in GitHub, Linear, and repo-local working-context files
broader human-facing notes can live in a non-repo context/archive folder
durable cross-machine memory belongs in the knowledge base, not in a shadow repo workspace

When to Use

User wants to save information to their knowledge base
Ingesting documents, conversations, or data into structured storage
Syncing knowledge across systems (local files, MCP memory, Supabase, Git repos)
Deduplicating or organizing existing knowledge
User says "save this to KB", "sync knowledge", "what do I know about X", "ingest this", "update the knowledge base"
Any knowledge management task beyond simple memory recall

Knowledge Architecture

Layer 1: Active execution truth

Sources: GitHub issues, PRs, discussions, release notes, Linear issues/egc-projects/egc-docs
Use for: the current operational state of the work
Rule: if something affects an active engineering plan, roadmap, rollout, or release, prefer putting it here first

Layer 2: Gemini CLI Memory (Quick Access)

Path: ~/.gemini/egc-projects/*/memory/
Format: Markdown files with frontmatter
Types: user preferences, feedback, project context, reference
Use for: quick-access context that persists across conversations
Automatically loaded at session start

Layer 3: MCP Memory Server (Structured Knowledge Graph)

Access: MCP memory tools (create_entities, create_relations, add_observations, search_nodes)
Use for: Semantic search across all stored memories, relationship mapping
Cross-session persistence with queryable graph structure

Layer 4: Knowledge base repo / durable document store

Use for: curated durable notes, session exports, synthesized research, operator memory, long-form docs
Rule: this is the preferred durable store for cross-machine context when the content is not repo-owned code

Read the full file on GitHub · 155 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.

1mo ago First seen · 155 lines · 53 tokens per session scan A eec2abefab55

Subscribe to this mod's changes

knowledge-ops is a skill published in the GitHub repository Jamkris/everything-gemini-code (91 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,418 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to knowledge-ops, differing in 16 lines, and is treated as a copy.

Memory and context Research ai-agents antigravity developer-tools gemini-cli gemini-cli-extension gemini-cli-skills

wiki

Daniel's Zettelkasten knowledge engine — 9 verbs (ingest/query/save/lint/manage/synthesize/critique/compare/eli5) unified in one namespace. Realizes Karpathy's LLM Wiki Compiler·Runner cycle beyond simple storage: synthesis, self-critique, comparison, and plain explanation. Triggers on: "/wiki", "wiki ingest", "wiki…

daniel8824-del/claude-wiki-verbs · 168 tokens

memory-management

This skill should be used when the user wants to "persist agent state", "remember past conversations", "short-term memory", "long-term memory", "session management", "vector database for agents", "agent memory", "context window management", "store user preferences", "recall previous interactions", "stateful agents"…

hajekim/agentic-design-patterns-skills · 418 tokens

knowledge-ops