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 Sixz-AI/repo-knowledge --skill rk-memogit clone --depth 1 https://github.com/Sixz-AI/repo-knowledgeWrote 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/sixz-ai/repo-knowledge/rk-memo)<a href="https://agentmods.dev/skills/sixz-ai/repo-knowledge/rk-memo"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-memo/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/sixz-ai/repo-knowledge/rk-memo"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-memo.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.00086 | $0.00790 |
| Opus 5 | $0.00043 | $0.00395 |
| Sonnet 5 | $0.00017 | $0.00158 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
rk-memo 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 11d 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.
RK Memo — Save Personal Knowledge
Store a piece of personal knowledge that isn't tied to any codebase.
Input
Free-form: <title>: <content> or just natural text describing what to save.
Step 1: Resolve home directory (cross-platform)
python3 -c "import os; print(os.path.expanduser('~'))"
Store as {HOME}. Base path: {HOME}/.repo-knowledge.
Step 2: Initialize _personal project if it doesn't exist
Check if {HOME}/.repo-knowledge/_personal/ exists.
If not, create it:
Use Write tool to create {HOME}/.repo-knowledge/_personal/_meta.md:
type: personal
git_url: none
created: {YYYY-MM-DD}
last_update: {YYYY-MM-DD}
total_docs: 0
Use Write tool to create {HOME}/.repo-knowledge/_personal/_index.md:
# _personal Knowledge Index
Add entry to {HOME}/.repo-knowledge/_registry.md:
| _personal | (personal) | {YYYY-MM-DD} | 0 |
Also create the docs directory by writing a placeholder if needed.
Step 3: Derive doc filename
Convert the title to kebab-case:
- Lowercase
- Replace spaces and special characters with
- - Remove consecutive dashes
Example: kubectl 查看 pod 状态 → kubectl-pod-status
Check if {HOME}/.repo-knowledge/_personal/docs/<kebab-name>.md already exists.
If it exists: this is an update — overwrite the existing doc.
If not: this is a new entry.
Step 4: Write the doc
Use Write tool to save {HOME}/.repo-knowledge/_personal/docs/<kebab-name>.md:
---
cached: {YYYY-MM-DD}
source: personal
---
## {title}
{content}
Keep content exactly as the user provided. If the user gave a code snippet, preserve it as a fenced code block with appropriate language tag.
Step 5: Update _index.md
For new entries: append to {HOME}/.repo-knowledge/_personal/_index.md:
- [{title}](docs/<kebab-name>.md) — {one-line summary}
aliases: [{title}, {key terms extracted from content}]
For existing entries (update): find the line with this doc path and update the description. Keep existing aliases, prepend the new title as alias if it changed.
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.
- 11d ago First seen · 109 lines · 86 tokens per session scan A a44a57789744
rk-memo is a skill published in the GitHub repository Sixz-AI/repo-knowledge (2 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 790 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.
Other skills, from other repositories
session-handoff
Create consistent session handoff documents for context transfer between sessions. Use when closing a session, reaching 75% token consumption, or when user requests handoff. Ensures proper YAML headers for metrics collection, LF line endings, and complete documentation of progress, decisions, and next steps.
memory
Memory discipline. Load when the agent keeps persistent memory across sessions - CLAUDE.md, AGENTS.md, auto-memory, memory banks, or any notes file the next session will read. Covers writing selectively, never recording what the repo already knows, structuring memory as index plus topics, stamping claims that can go…
code-to-docs-digest
Load existing code-to-docs vault context into the conversation before coding. Read-only — never writes files. Provides architecture overview, module summaries, known issues, and session history. Use when starting a coding session, loading doc context, or catching up on a documented codebase.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive-mine
Nightly scan of session transcripts -- extract decisions, tasks, people, insights.
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.