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-listgit 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-list)<a href="https://agentmods.dev/skills/sixz-ai/repo-knowledge/rk-list"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-list/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-list"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-list.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.00054 | $0.00222 |
| Opus 5 | $0.00027 | $0.00111 |
| Sonnet 5 | $0.00011 | $0.00044 |
| Haiku 4.5 | $0.00005 | $0.00022 |
Grade A, and why
rk-list 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 10d 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.
What it actually says
RK List — List All Knowledge Bases
Show all registered codebase knowledge bases.
Process
- Read
~/.repo-knowledge/_registry.md - For each project row, check
~/.repo-knowledge/<project>/_meta.mdfortypefield:type: personal→ show as(personal)in the Git URL column- No type /
type: repo→ show the git URL as normal
- Format and display the table to the user
- If registry is empty or doesn't exist, tell the user:
"No knowledge bases found. Use
/repo-knowledge:rk-create <git-url>to create one, or/repo-knowledge:rk-memoto save personal knowledge."
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.
- 10d ago First seen · 19 lines · 54 tokens per session scan A f2a995162e45
rk-list is a skill published in the GitHub repository Sixz-AI/repo-knowledge (2 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 222 once invoked, about $0.0003 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
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.