knowledge-agent

knowledge-agent is a skill for Claude Code, Codex from thedotmack/claude-mem. It costs 46 tokens per session (569 once invoked), scanned A, original, Apache-2.0.

A knowledge-base guide that collects selected claude-mem observations into a focused collection and loads them into an AI session. These collections act like topic-specific reference sets, such as past decisions about hooks or bug fixes for one service.

In plain words
What is it for?
Use it to build and load focused collections, then investigate earlier decisions, bugs, features, refactors, discoveries, or changes in a chosen topic or part of a project.
Why use it?
It helps you ask questions about a narrow area of past work without searching through every saved observation. You can filter the collection by project, note type, topic, files, search terms, or dates.

Skill for Claude CodeCodex

Part of the claude-mem plugin — 16 skills, 1 MCP server shipped together

About the project

Claude-Mem, now presented as Grok Mem, records an agent's work, compresses it with AI, and brings relevant notes into later sessions so the agent can remember decisions and next steps. It is intended for persistent context across agent conversations and supports multiple coding-agent environments. The catalogue add-ons provide the workflows and integrations used to operate this memory system.

thedotmack/claude-mem · 93,205 stars · on GitHub

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.

agentmods
npx agentmods add skills/thedotmack/claude-mem/knowledge-agent
Any agent
npx skills add thedotmack/claude-mem --skill knowledge-agent
Clone the repo
git clone --depth 1 https://github.com/thedotmack/claude-mem

Made for: Claude Code, Codex.

Or install claude-mem, the plugin that ships this one along with the rest of its 16 skills, 1 MCP server.

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.

agentmods badge for knowledge-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/thedotmack/claude-mem/knowledge-agent.svg)](https://agentmods.dev/skills/thedotmack/claude-mem/knowledge-agent)
Your own site
<a href="https://agentmods.dev/skills/thedotmack/claude-mem/knowledge-agent"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/knowledge-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 569 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00569
Opus 5 $0.00023 $0.00284
Sonnet 5 $0.00009 $0.00114
Haiku 4.5 $0.00005 $0.00057

Measured 5d ago against content hash 538de006ebe2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

knowledge-agent 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 5d 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

Copies of this mod

1 near-identical copy found in the catalogue:

plugin/skills/knowledge-agent/SKILL.md · 81 lines

How it starts

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

Knowledge Agent

Build and query AI-powered knowledge bases from claude-mem observations.

What Are Knowledge Agents?

Knowledge agents are filtered corpora of observations compiled into a conversational AI session. Build a corpus from your observation history, prime it (loads the knowledge into an AI session), then ask it questions conversationally.

Think of them as custom "brains": "everything about hooks", "all decisions from the last month", "all bugfixes for the worker service".

Workflow

Step 1: Build a corpus

build_corpus name="hooks-expertise" description="Everything about the hooks lifecycle" project="claude-mem" concepts="hooks" limit=500

Filter options:

  • project — filter by project name
  • types — comma-separated: decision, bugfix, feature, refactor, discovery, change
  • concepts — comma-separated concept tags
  • files — comma-separated file paths (prefix match)
  • query — semantic search query
  • dateStart / dateEnd — ISO date range
  • limit — max observations (default 500)

Step 2: Prime the corpus

prime_corpus name="hooks-expertise"

This creates an AI session loaded with all the corpus knowledge. Takes a moment for large corpora.

Step 3: Query

query_corpus name="hooks-expertise" question="What are the 5 lifecycle hooks and when does each fire?"

The knowledge agent answers from its corpus. Follow-up questions maintain context.

Step 4: List corpora

list_corpora

Shows all corpora with stats and priming status.

Tips

  • Focused corpora work best — "hooks architecture" beats "everything ever"
  • Prime once, query many times — the session persists across queries
  • Reprime for fresh context — if the conversation drifts, reprime to reset
  • Rebuild to update — when new observations are added, rebuild then reprime

Maintenance

Rebuild a corpus (refresh with new observations)

rebuild_corpus name="hooks-expertise"

After rebuilding, reprime to load the updated knowledge:

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

  1. 5d ago First seen · 81 lines · 46 tokens per session scan A 538de006ebe2

Subscribe to this mod's changes

knowledge-agent is a skill published in the GitHub repository thedotmack/claude-mem (93,205 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 569 once invoked, about $0.0002 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.