Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aigentive/RalphX/plugin install ralphxWrote 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/aigentive/ralphx/knowledge-capture)<a href="https://agentmods.dev/skills/aigentive/ralphx/knowledge-capture"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/knowledge-capture/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/aigentive/ralphx/knowledge-capture"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/knowledge-capture.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.00070 | $0.00805 |
| Opus 5.5 | $0.00028 | $0.00322 |
| Sonnet 5.5 | $0.00014 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
knowledge-capture 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Capture
Packages session learnings into scoped .claude/rules/ files.
Step 1: Read Framework Reference
Read the memory framework doc for knowledge capture criteria and format:
${CLAUDE_PLUGIN_ROOT}/memory-framework.md
Also fetch/refresh the official Claude Code memory docs (cached locally):
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-fetch-docs.sh"
Step 2: Evaluate Session
Review the current session's conversation to identify:
Worth Capturing
- Complex multi-component interactions (e.g., "Component A triggers Event B which updates State C")
- Error recovery procedures that took multiple attempts to resolve
- Deep internal system knowledge (state machines, data flows, edge cases)
- Framework/library quirks and workarounds (e.g., React ref equality, Tauri serialization)
- Patterns that would save >15 minutes if known upfront next time
NOT Worth Capturing
- One-off fixes unlikely to recur
- Knowledge already documented in existing .claude/rules/ files
- Generic programming knowledge (things Claude already knows)
- Temporary workarounds that should be fixed properly
- Simple bug fixes with obvious causes
If nothing worth capturing -> output "No significant learnings to capture." and stop.
Step 3: Classify Each Learning
For each learning worth capturing, determine:
3a. Scope (which files does it relate to?)
- Identify the files that were involved in the discovery
- Determine glob patterns that cover those files
- Example: discovery about TaskGraph -> paths: ["src/components/TaskGraph/**"]
3b. Existing Rule Check
Run the audit script to see current rules:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-audit.sh" --json
Check if any existing rule file covers the same domain:
- If yes -> append to that file (add new ## section)
- If no -> create new file
3c. Format Entry
Use the auto-memory style format:
## [Descriptive Title]
- **Problem**: What went wrong or was complex
- **Fix**: How it was resolved
- **File**: Key file paths involved (e.g., `src/components/TaskGraph/TaskGraphView.tsx`)
- **Pattern**: Reusable principle (if applicable)
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 · 109 lines · 70 tokens per session scan A 1878b16decda
knowledge-capture is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 70 tokens to every session and 805 once invoked, about $0.0003 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.