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/janyork/llm-wiki-cli/using-syncnpx skills add JanYork/llm-wiki-cli --skill using-syncgit clone --depth 1 https://github.com/JanYork/llm-wiki-cliWhat 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.00033 | $0.02115 |
| Opus 5 | $0.00016 | $0.01058 |
| Sonnet 5 | $0.00007 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
using-sync 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 3d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using LWC Sync
Run Sync through the audited CLI only:
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
Every start, resume, resolve, abort, pull, push, or merge can publish or change durable data. Before the first execution in a bounded workflow, present a safety notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility. An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.
One authorization covers the bounded workflow while its host, directory, scope,
mode, publication targets, and disclosed risks remain unchanged. It covers
read-only preflight, prerequisite build and installation, the initial Sync,
ordinary --resume, continuity or derived recovery, status checks, and an abort
before publication. Equivalent command details that do not widen the target or
risk do not require reconfirmation.
Reconfirm only when a host, directory, scope, mode, or publication target changes; a new destructive, irreversible, privacy, or data-loss risk appears; or a candidate resolution would discard one side. Preserve-both and idempotent recovery within the same session remain covered. A Skill trigger alone is not authorization.
Choose the scope explicitly before starting:
--scope projectsynchronizes only the active project Wiki. Supply the remote project's absolute directory when it cannot be discovered from the remote login directory.--scope globalsynchronizes only the global Wiki; omit the directory.--scope allsynchronizes project and global stores as one coordinated session. Supply the remote project's absolute directory.
Use merge to publish the reconciled result to both sides, pull to publish it only locally, and push to publish it only remotely. Every mode preserves unique semantic objects from both sides; direction controls the destination, not destructive authority. Scope and mode are session invariants: keep the exact original --scope, HOST, optional ABS_DIRECTORY, and --mode on every continuation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 159 lines · 33 tokens per session scan A 8fead4fcb1e4
using-sync is a skill published in the GitHub repository JanYork/llm-wiki-cli (48 stars, last pushed 7d ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,115 once invoked, about $0.0002 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
static
Stash is your personal home for agent work. Everything you create is scoped to your account — it is yours alone, with nothing to pick or set up first. Your Stash has three primary surfaces.
brief
Brief the user on what they saved in a period — the thread running through it, not a list.
aidd-refine:03:condense
Toggle terse output mode with intensity levels (lite, full, ultra) so prose drops articles, filler, and pleasantries while code, quoted errors, and security warnings stay verbatim. Use when the user says "condense", "condense output", "be more concise", "shorter answers", "tighten output", "/condense", "/condense…
aidd-pm:04:clarity
Ultra-compressed communication mode. Cuts token usage 75% while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra. Toggle on/off by invoking /clarity again. Use when user says "clarity", "less tokens", "be brief", or invokes /clarity.
cleanup
Find duplicates, dead links and untagged items in a saved library and propose what to do about each.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.