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 LevNas/ccmemo --skill record-knowledgegit clone --depth 1 https://github.com/LevNas/ccmemoWrote 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/levnas/ccmemo/record-knowledge)<a href="https://agentmods.dev/skills/levnas/ccmemo/record-knowledge"><img src="https://agentmods.dev/badge/skills/levnas/ccmemo/record-knowledge/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/levnas/ccmemo/record-knowledge"><img src="https://agentmods.dev/badge/skills/levnas/ccmemo/record-knowledge.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00092 | $0.00674 |
| Opus 5.5 | $0.00037 | $0.00270 |
| Sonnet 5.5 | $0.00018 | $0.00135 |
| Haiku 4.5 | $0.00009 | $0.00067 |
Grade A, and why
record-knowledge 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record Knowledge
Goal
Capture tacit knowledge discovered during work and make it available for future sessions.
When to Reference
- New session start: Search
.claude/knowledge/entries/for active entries related to the current task before starting work- If an
overviewentry exists for the topic, read it first — loaddetailentries on demand to save context
- If an
- Progress update: Check if related entries need updating based on new discoveries
- Not needed when resuming a session (context is already preserved)
Execution
Delegate the recording work to a subagent to minimize main context consumption.
- Analyze the user input or work context and prepare structured input fields
- Determine the knowledge base path (default:
.claude/knowledge/entries/) - Spawn a subagent with the following configuration:
Agent(
subagent_type: "general-purpose",
description: "record knowledge entry",
prompt: |
You are a knowledge recording agent. Read the procedure file and follow it precisely.
## Input
### what(事実)
{what}
### why(判断理由)
{why}
### context(背景情報)
{context}
### tags_hint(推奨タグ)
{tags_hint}
## Instructions
1. Read the procedure file at: {plugin_root}/skills/record-knowledge/procedure.md
2. Follow the procedure step by step
3. The knowledge base is at: {project_root}/.claude/knowledge/
4. Return: filename, # heading, ## headings, and linked entries
)
Replace the placeholders:
{what}— 何が起きたか: the factual observation, discovery, or decision to record{why}— なぜ重要か: why this matters, the reasoning behind recording it (judgment made by the main agent){context}— 関連する背景情報: surrounding context (task being worked on, environment, related files, issues){tags_hint}— 推奨タグ: tags the main agent recommends (subagent validates against the tag registry){plugin_root}— the plugin's installation path (shown in the skill loading message as "Base directory for this skill"){project_root}— the project working directory
What ships with it
2 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.
- 1mo ago First seen · 71 lines · 92 tokens per session scan A 397a57304e7b
record-knowledge is a skill published in the GitHub repository LevNas/ccmemo (4 stars, last pushed 11d ago), licensed MIT. It adds 92 tokens to every session and 674 once invoked, about $0.0004 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-31.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
handoff
Create a structured session handoff when context is running low or work is pausing. Deep context mining, self-validation, multi-file splitting. Captures everything the next session needs.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.