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/lexfrei/ccc/worksyncnpx skills add lexfrei/ccc --skill worksyncgit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00183 | $0.01176 |
| Opus 5 | $0.00092 | $0.00588 |
| Sonnet 5 | $0.00037 | $0.00235 |
| Haiku 4.5 | $0.00018 | $0.00118 |
Grade A, and why
worksync 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
worksync — log a sync-worthy entry
Appends a single timestamped bullet to today's note at
${WORKSYNC_VAULT_DIR:-$HOME/worksync}/YYYY-MM-DD.md via the bundled helper
script ${CLAUDE_PLUGIN_ROOT}/scripts/worksync-append.sh.
The file's purpose: a low-friction daily log of things the user will want to mention at a work sync, standup, or weekly review. Phrase entries for a technical peer audience.
Arguments
The skill accepts a free-form argument from $ARGUMENTS:
- If non-empty: treat it as the message, with optional leading type hint.
- If empty: derive message from recent session activity (see "Inferring content" below).
Supported types (passed as first arg to the helper):
| Type | When to use |
|---|---|
research |
A question was investigated and produced a concrete finding or decision. |
ops |
A deploy, rollout, migration, or infrastructure operation finished. |
checkpoint |
User-requested mid-task marker ("log this", "checkpoint"). |
note |
Anything else worth mentioning that doesn't fit the above. |
Types pr, issue, merge are reserved for the automatic hook — do not
emit them from the skill. If the user explicitly asks to log one manually, use
note and include the URL in the message.
Inferring content (no arguments case)
When invoked with no arguments, scan the most recent turns of the current session and produce ONE entry summarizing the most recent sync-worthy event. Do not produce multiple entries in one invocation — call the skill again if more is needed.
Selection priority (pick the most recent qualifying item):
- An
opsaction that visibly succeeded (deploy, apply, rollout, migration, infrastructure reconfiguration, provisioning run against real hosts). - A
researchconclusion — user asked a question, you investigated, you reached a definite answer or recommendation. - A
checkpointthe user explicitly requested.
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.
- 2d ago First seen · 117 lines · 183 tokens per session scan A 1e34f925d09b
worksync is a skill published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 183 tokens to every session and 1,176 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…