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/everyone-needs-a-copilot/claude-copilot/setup-knowledge-syncnpx skills add Everyone-Needs-A-Copilot/claude-copilot --skill setup-knowledge-syncgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/setup-knowledge-sync)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/setup-knowledge-sync"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/setup-knowledge-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.00030 | $0.00190 |
| Opus 5 | $0.00015 | $0.00095 |
| Sonnet 5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
setup-knowledge-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 yesterday.
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.
What it actually says
Setup Knowledge Sync
Set up a safe knowledge synchronization path.
Workflow
- Verify the project is a git repository.
- Inspect
cc config list --scope effectivewhen available. - Check
paths.knowledge_repoandrefs.*. - If a knowledge repository exists, verify its manifest and docs index.
- If no repository exists, create a plan for a Git-friendly knowledge repo with a manifest, docs index, and memory/reference policy.
- Use
scripts/activate-pack.pyonly for explicit pack activation. - Do not delete, replace, or rewrite existing knowledge repositories without explicit current approval.
Output
- knowledge sync mode
- config updates
- manifest or docs gaps
- safe activation commands
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.
- yesterday First seen · 26 lines · 30 tokens per session scan A c8c6f9e16805
setup-knowledge-sync is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 190 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-09-04.
Other skills, from other repositories
go-start
Session startup skill. Reads platform docs, builds context, asks which project we're working on, reads project docs — and is ready to work. Also handles continuation of a stuck task by restoring context from the interrupted session. Use when: start of a new terminal session, load context, resume interrupted work.
gohm
/gohm - Go Harvest Memory (Knowledge Harvester).
memory
Use this agent to manage permanent memory storage, retrieval weight calculation, and knowledge preservation following NASAB Pillar 5.
context
Context Manager - Token Budget Controller.
recall
/recall — Layered Knowledge Recall.
abmind_recall_workaround
Fallback when abmind recall / the abmindrecall tool fails — read memories directly from the SQLite DB.