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-remote-initgit 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-remote-init)<a href="https://agentmods.dev/skills/sixz-ai/repo-knowledge/rk-remote-init"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-remote-init/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-remote-init"><img src="https://agentmods.dev/badge/skills/sixz-ai/repo-knowledge/rk-remote-init.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.00095 | $0.00779 |
| Opus 5 | $0.00048 | $0.00390 |
| Sonnet 5 | $0.00019 | $0.00156 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
rk-remote-init 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RK Remote Init — Initialize Remote Sync
Link the local knowledge base to a user-provided remote git repository.
Security warning: The remote repository will contain documentation that includes code snippets from your indexed projects. Always use a private repository.
Input
- Git remote URL (SSH or HTTPS, e.g.
[email protected]:user/my-knowledge.git)
Step 1: Resolve home directory (cross-platform)
python3 -c "import os; print(os.path.expanduser('~'))"
Store result as {HOME}. Use {HOME}/.repo-knowledge as the base path for all operations.
Step 2: Ensure base directory exists
Use the Write tool to create {HOME}/.repo-knowledge/_registry.md if it does not already exist (this also creates the directory). Content if creating new:
# RepoKnowledge Registry
| Project | Git URL | Last Update | Docs |
|---------|---------|-------------|------|
Step 3: Check if already a git repo
git -C {HOME}/.repo-knowledge rev-parse --git-dir 2>/dev/null && echo "yes" || echo "no"
If not a git repo, initialize:
git -C {HOME}/.repo-knowledge init
git -C {HOME}/.repo-knowledge checkout -b main 2>/dev/null || true
Step 4: Create .gitignore
Use Write tool to create {HOME}/.repo-knowledge/.gitignore:
_repos/
*.tmp
Step 5: Configure remote
git -C {HOME}/.repo-knowledge remote add origin <git-url> 2>/dev/null || \
git -C {HOME}/.repo-knowledge remote set-url origin <git-url>
Step 6: Detect whether remote already has data
git -C {HOME}/.repo-knowledge fetch origin main 2>/dev/null && echo "has_data" || echo "empty"
If remote already has data (subsequent machine setup):
Run the full merge flow from rk-pull (Steps 3–7 of rk-pull) to bring remote knowledge into local before pushing.
Then:
git -C {HOME}/.repo-knowledge push -u origin main
If remote is empty (first machine):
git -C {HOME}/.repo-knowledge add -A
git -C {HOME}/.repo-knowledge commit -m "init: initial knowledge base" --allow-empty
git -C {HOME}/.repo-knowledge push -u origin main
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 · 97 lines · 95 tokens per session scan A 0c9ccad8963b
rk-remote-init is a skill published in the GitHub repository Sixz-AI/repo-knowledge (2 stars, last pushed 4mo ago), licensed MIT. It adds 95 tokens to every session and 779 once invoked, about $0.0005 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…
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…
open-pr
A helper for opening a new pull request, which is a request to merge changes from one Git branch into another. It pushes the current branch, chooses the target branch, and prepares a title and description for your confirmation.
worktree-done
A cleanup procedure for removing a Git worktree, returning the main checkout to its base branch, and deleting the related feature branch. A worktree is a separate working directory linked to the same Git repository.
start-branch
A Git workflow for creating and switching to a new branch, which is a separate line of work in a code repository. It chooses a name based on the task and can start from the current position or a named base branch.
branch-done
A Git cleanup workflow for deleting the current feature branch and returning to the project's base branch after a pull request is opened.