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 lexfrei/ccc/plugin install worksyncWrote 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/lexfrei/ccc/worksync)<a href="https://agentmods.dev/skills/lexfrei/ccc/worksync"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/worksync/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/lexfrei/ccc/worksync"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/worksync.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.00183 | $0.01156 |
| Opus 5.5 | $0.00073 | $0.00462 |
| Sonnet 5.5 | $0.00037 | $0.00231 |
| Haiku 4.5 | $0.00018 | $0.00116 |
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 1mo 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 — 98 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.
- 1mo ago Changed · -19 lines d806819ae3f9
- 1mo ago First seen · 117 lines · 183 tokens per session scan A 1e34f925d09b
worksync is a skill published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 183 tokens to every session and 1,156 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…