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 agentmods add skills/tpierrain/kenjaku/sync-sourcesnpx skills add tpierrain/kenjaku --skill sync-sourcesgit clone --depth 1 https://github.com/tpierrain/kenjakuWrote 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/tpierrain/kenjaku/sync-sources)<a href="https://agentmods.dev/skills/tpierrain/kenjaku/sync-sources"><img src="https://agentmods.dev/badge/skills/tpierrain/kenjaku/sync-sources.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.08039 |
| Opus 5 | $0.00042 | $0.04019 |
| Sonnet 5 | $0.00017 | $0.01608 |
| Haiku 4.5 | $0.00008 | $0.00804 |
Grade A, and why
sync-sources 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 5d 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 — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync sources — Fan-out/fan-in architecture (internal reference)
This is not a user command. This file documents the sub-agent architecture of Phase 2 of the main flow (sync sources in background — see
CLAUDE.md). You never trigger the pull by hand: it's the question that triggers it. Note:/syncis a separate command that synchronizes the git repo between machines.🔧 Adapt to your connectors. The examples below reference MCP tools generically (
mcp__<slack>__…,mcp__<drive>__…,mcp__<calendar>__…). Replace them with the real names of the connectors you've wired up (see SETUP §6). Without a wired connector, this skill does nothing — the RAG engine answers on its own from the vault.
Absolute constraint
READ-ONLY. Never send a message, an email, or a reaction. Never post in a channel. Produce only local markdown files in the vault.
Sub-agent tooling — NEVER a shell to process text
The sub-agents are LLMs: they read and summarize by reasoning, not via the shell.
Forbidden to use python3 -c, python, node -e, awk, sed, jq, grep, cat,
head, tail — or any Bash command — to parse, load, split, slice or summarize
content. Why this is non-negotiable (especially on Claude Desktop, Code tab):
- each ad-hoc command is unique → it re-triggers an authorization prompt on every call (endless prompts, impossible to pre-authorize);
- some (multi-line,
#inside an argument, redirections) are refused for security and don't even offer "Always allow" — the user cannot accept them.
Instead:
- Read content → the
Readtool (a vault file; or a large tool result that Claude offloaded to…/tool-results/…: read it withRead, not withpython3 -c "open(...)"). - Write the raw source / the briefing → the
Write/Edittools. - Split ("up to the Details section", "the first 4000 characters"…) → in your head, not in Python.
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.
- 5d ago First seen · 554 lines · 83 tokens per session scan A 33c9c3bcc687
sync-sources is a skill published in the GitHub repository tpierrain/kenjaku (80 stars, last pushed 11d ago), licensed Apache-2.0. It adds 83 tokens to every session and 8,039 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-30.
Other skills, from other repositories
lint
Run the LLM Wiki health check: orphans, broken links, contradictions, stale pages, index sync, MOC coverage, frontmatter fields, Exploration Gate, v5 verification fields, Bias Check, cross-vault links, and Core Context freshness; also responds to /lint and 위키 점검.
refresh-context
Re-snapshot Core Context.md from the 9 mothership system files and key essays when the mothership changes or the snapshot is older than 30 days; also responds to /refresh-context and 코어 컨텍스트 갱신.
status
Show the LLM Wiki state at a glance: counts, recent activity, index drift, inbox backlog, collectionPurpose/mainVault/explored/verificationStatus coverage, and Core Context snapshot age; also responds to /status and 상태 점검.
capture-tabs
Capture Chrome tab groups, browser research bundles, or ChatGPT/Gemini/Grok/Claude/Perplexity sessions into LLM Wiki Inbox markdown; also responds to 탭 캡처, 리서치 캡처, Deep Research 캡처, and /capture-tabs.
reindex
Manually re-run qmd indexing and embeddings for wiki, rawsources, and queries after Obsidian edits, bulk moves, or embedding-model changes; also responds to /reindex and 재색인.
ingest
Ingest a URL, file, raw text, or Inbox item into the LLM Wiki with the purpose gate, mothership link search, raw-source preservation, Wiki compilation, index/log update, and review; also responds to /ingest and 인제스트.