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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.00259 |
| Opus 5.5 | $0.00012 | $0.00104 |
| Sonnet 5.5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 6d 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.
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
Work Lifecycle
Apply the shared work lifecycle once per task, including direct invocation of this skill: start/resume, maintain, pause/handoff, finish and later reuse. Keep the checkpoint proportional in the existing record; a small answer does not need a new task or document.
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.
- 6d ago Changed 396cb6786320
- 7d ago Changed · +7 lines 4a7c6f37223b
- 1mo ago 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 (14 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 259 once invoked, about $0.0001 per session on Opus 5.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
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
harness-step3-session-management
A project setup for keeping an agent’s work state in files between separate chat sessions. It creates a task list, a progress summary, and a script for checking the project environment.
sweep-now
Run the three read-mostly vault sweeps for stale tracker items, dormant-note candidates, and broken wikilinks, then append one dated result to SWEEPLOG.md.
operator-setup
The AIgent first-run operator-business interview. Learn the operator's business in three plain questions, write the first memory, and play back a briefing that reads personal, not templated. This is the "it remembers me" moment. A distinct skill that LAYERS ON TOP of the base /setup (which is left intact), it does not…