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-pushgit 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-push)<a href="https://agentmods.dev/skills/sixz-ai/repo-knowledge/rk-push"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-push/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-push"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-push.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.00087 | $0.00981 |
| Opus 5 | $0.00044 | $0.00491 |
| Sonnet 5 | $0.00017 | $0.00196 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
rk-push 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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RK Push — Sync Local Knowledge Base to Remote
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: Check remote is configured
Read {HOME}/.repo-knowledge/_remote.md.
If not found: tell user to run /repo-knowledge:rk-remote-init <git-url> first. Stop.
Step 3: Fetch remote
git -C {HOME}/.repo-knowledge fetch origin main
Step 4: Check if remote has new commits
git -C {HOME}/.repo-knowledge rev-list HEAD..origin/main --count
If count > 0, remote is ahead — proceed to Step 5 (merge). If count = 0, no remote changes — skip to Step 8.
Step 5: Identify changed files
git -C {HOME}/.repo-knowledge diff HEAD origin/main --name-only
Step 6: Agent merge for each changed file
Process each file from the diff. Use git -C {HOME}/.repo-knowledge show origin/main:<relative-path> to read the remote version of any file.
_registry.md
- Read local
{HOME}/.repo-knowledge/_registry.md - Read remote:
git -C {HOME}/.repo-knowledge show origin/main:_registry.md - Merge: union of all data rows, deduplicate by project name (first column), keep the row with the most recent
Last Updatedate for duplicates - Write merged result with Write tool
<project>/_index.md
- Read local version
- Read remote:
git -C {HOME}/.repo-knowledge show origin/main:<project>/_index.md - Parse entries — each entry is identified by its doc path (the
(path/to/file.md)part) - Merge:
- Same doc path in both: union of alias lists, deduplicate, keep first 10 (local aliases go first as they are more recent)
- Only in remote: append to local
- Only in local: keep as-is
- Write merged
_index.md
<project>/docs/*.md (any doc file)
- Read local file frontmatter (
cached:field) - Read remote version frontmatter:
git -C {HOME}/.repo-knowledge show origin/main:<path> - Keep whichever has the newer
cached:date - If remote is newer: overwrite local with Write tool
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.
- 9d ago First seen · 108 lines · 87 tokens per session scan A 8b4277839209
rk-push is a skill published in the GitHub repository Sixz-AI/repo-knowledge (2 stars, last pushed 4mo ago), licensed MIT. It adds 87 tokens to every session and 981 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
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…
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.
recall
Answer "why" and "when" questions about a project's decisions — the intent behind a past choice, when it was made, what was tried before and rejected. Use when asked why something was decided, what the rationale was, or before reversing or redoing earlier work. For why the code mechanically behaves a certain way use…
session-handoff-number-collision-with-unmerged-sibling
Detect and recover from a session-number collision when running session-handoff and a parallel/sibling session has authored a same-numbered handoff doc that hasn't merged into main yet. Use when: (1) you're in session-handoff Phase 1 about to write docs/handoffs/sessionNNNhandoff.md, (2) ls docs/handoffs/ shows the…
writing-github-docs
Write the repository's public face — README.md, CONTRIBUTING.md, and the GitHub community health files (SECURITY, CODEOFCONDUCT, LICENSE, issue and pull request templates). Use this when creating or rewriting any of those, when deciding whether a sentence belongs in the README or in CONTRIBUTING, when GitHub's…
brain-hydrate
Use when users want to bootstrap the brain with existing project knowledge -- reading ADRs, feature specs, UX docs, commit history, and error patterns to seed institutional memory on a project that already has artifacts on disk. Also use for incremental re-hydration after significant work outside the pipeline.…