Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add odere-pro/claude-wiki-pages-plugin/plugin install claude-wiki-pagesWrote 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/odere-pro/claude-wiki-pages-plugin/sync)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/sync"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/sync.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.1 | $0.00087 | $0.01021 |
| Opus 5 | $0.00044 | $0.00511 |
| Sonnet 5 | $0.00017 | $0.00204 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
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 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Sync
Bring the wiki up to date with a wired source repository. Detection and copying are deterministic scripts; this skill's judgment is confined to marking superseded source notes and reporting.
What a sync is — and is not
A wired source is a git work tree (usually the host project) registered in
settings.json with docs-only include globs. Sync detects upstream changes
with git diff --name-only <lastSyncedCommit>..HEAD, copies changed docs
into raw/wired/<name>/ as NEW versioned snapshots (raw is immutable — an
updated doc never overwrites its earlier snapshot), and leaves re-ingest to
the normal pipeline. Sync itself never writes wiki pages — pages update
when ingest processes the new snapshots (additive merge per the dedup rules).
Workflow
- Snapshot pre. Run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/snapshot.sh pre --target <vault>— git-checkpoint the vault before any sync write. Always exits 0. - Status. Run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/sync-source.sh status. Report theWIRED-CHANGES: <name> <N>lines to the user. If every count is 0, stop here: report "wiki is in sync" and skip steps 3–7. - Confirm. Show the changed-file list and ask before pulling. The pull
is additive-only (new files in
raw/), but the user decides when wiki content refreshes. - Pull. Run
bash ${CLAUDE_PLUGIN_ROOT}/scripts/sync-source.sh pull [--name <n>]. This snapshots changed docs (versioned<stem>--<date>-<sha8>siblings, checksum-deduped), then records the wired repo's HEAD as the new sync point. - Mark superseded source notes. For each versioned snapshot the pull
created: if an earlier snapshot of the same doc was already ingested (its
summary exists in
wiki/_sources/), Edit that summary's frontmatter to addsuperseded_by: "[[<new snapshot title>]]"and append one body line:> Superseded by a newer snapshot of this document — see [[<new>]].Do not changesources:on wiki pages — provenance history stays intact; ingest's additive merge appends the new source when the pages refresh. - Log. Append to
vault/wiki/log.md:
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 · 83 lines · 87 tokens per session scan A c6f34f2e7d66
sync is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 1,021 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
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
add-sharepoint
Adds SharePoint Online connector to a Power Apps code app. Use when reading lists, managing documents, or integrating with SharePoint sites. Can also create new SharePoint lists.
add-pdf-viewer
Internal implementation skill invoked by /add-native for native PDF control workflows. Handles HTTPS and file URI PDF viewing with @microsoft/power-apps-native-pdf-viewer 0.2.9+.
add-excel
Adds Excel Online (Business) connector to a Power Apps code app. Use when reading or writing Excel workbook data from OneDrive or SharePoint.
add-onedrive
Adds OneDrive for Business connector to a Power Apps code app. Use when uploading, downloading, listing, or managing files in OneDrive.
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…