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/curt-park/autology/sync-knowledgenpx skills add Curt-Park/autology --skill sync-knowledgegit clone --depth 1 https://github.com/Curt-Park/autologyWrote 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/curt-park/autology/sync-knowledge)<a href="https://agentmods.dev/skills/curt-park/autology/sync-knowledge"><img src="https://agentmods.dev/badge/skills/curt-park/autology/sync-knowledge.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.00063 | $0.01088 |
| Opus 5 | $0.00032 | $0.00544 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
sync-knowledge 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 4d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
docs/ nodes must accurately reflect the actual codebase and decisions. This skill verifies that and fixes any discrepancies in-place.
Two modes:
- Fast (default): verifies only the nodes triage identified — fast enough to run after every action.
- Full: audits the entire codebase and knowledge base independently — for periodic reviews or when explicitly requested.
Precondition: if triage has not run this session, run /autology:triage-knowledge first, then fast sync. Full mode is only used when the user explicitly passes full.
Quick Reference
/autology:sync-knowledge # fast — verifies nodes triage identified
/autology:sync-knowledge full # full audit — no triage needed
Fast Mode
Precondition: triage has already run and returned matched existing nodes.
1. Receive Triage Output
Use triage's matched nodes as the sync scope:
Existing nodes from triage (→ sync):
- docs/foo.md — matches [item description]
Connected: [[bar]], [[baz]] | Tags: arch, api
Also include any connected nodes listed in the topology hints.
2. Verify and Fix
For each matched doc:
- Read the doc
- Read the changed code file
- Compare: do counts, names, types, paths, and behavior claims still match?
- If discrepancies found: edit the doc in-place to reflect current reality
3. Report
## Sync Report (fast)
**Changed files checked**: N
**Docs matched**: N
**Docs updated**: N
### Updated
- docs/example.md — updated function count (3 → 4)
### No changes needed
- docs/other.md — still accurate
If no docs reference any changed file: "No docs reference the changed files — nothing to sync."
Full Mode
1. Read All Nodes
Glob: docs/*.md
Read: each file (frontmatter + content)
Extract: title, type, tags, content, wikilinks ([[target]] patterns)
2. Survey Codebase
Identify the project's key files based on its structure:
Glob: common project manifests (package.json, go.mod, Cargo.toml, pyproject.toml, etc.)
Glob: source directories identified from project structure
Read: key config files (hooks/, scripts/, config/, etc.)
What ships with it
2 files 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.
- 4d ago First seen · 147 lines · 63 tokens per session scan A efc3313113b7
sync-knowledge is a skill published in the GitHub repository Curt-Park/autology (24 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,088 once invoked, about $0.0003 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
mama-context
Always-on background context injection from MAMA memory. Automatically surfaces relevant decisions when you work on code, without explicit invocation.
open-zk-kb
This skill should be used when the user asks to "store a note", "save this to the knowledge base", "remember this", "search my notes", "what do I know about X", "review stale notes", "how many notes", "KB stats", "mine sessions", "ingest a URL", "open Obsidian", "what template for a decision", or mentions knowledge…
mama-install
Install MAMA OS and follow its self-teaching CLI until the first report is confirmed.
vault
Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.
kb-session-review
Review this session's knowledge base usage. Use when the user asks whether the KB was updated, what was captured, if anything was missed, or wants a session retrospective on knowledge capture quality.
entry-authoring
Use when writing or editing LibrAIum data entries (data/entries//.md) — house style for summaries, Reception, Personal Notes, tags, and metadata.