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.
git clone --depth 1 https://github.com/lexfrei/cccWrote 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/plugins/lexfrei/ccc/worksync)<a href="https://agentmods.dev/plugins/lexfrei/ccc/worksync"><img src="https://agentmods.dev/badge/plugins/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/plugins/lexfrei/ccc/worksync"><img src="https://agentmods.dev/badge/plugins/lexfrei/ccc/worksync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
What it actually says
{
"name": "worksync",
"version": "0.2.1",
"description": "Automatic daily work-sync log — PostToolUse hook captures gh pr/issue create/merge/close, and a companion skill lets Claude log research/ops/checkpoint events into a dated markdown note (feeds standups via Obsidian/Logseq/plain markdown)",
"author": {
"name": "Aleksei Sviridkin",
"email": "[email protected]"
},
"repository": "https://github.com/lexfrei/ccc",
"keywords": ["hooks", "skills", "productivity", "standup", "obsidian", "markdown", "github"],
"userConfig": {
"vault_dir": {
"title": "Worksync note directory",
"type": "string",
"description": "Absolute path to the directory where daily work-sync notes will be written. Examples: ~/Documents/Obsidian/<vault>/worksync, ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/<vault>/worksync. Leave blank to use ~/worksync.",
"sensitive": false
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 183 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 4b5103f70e3b
- 1mo ago First seen · 20 lines scan A a4ee9a361bce
worksync is a plugin published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
statusline-for-claude-code
A dependency-free Node.js status line for Claude Code: model and effort, live git state, context window, prompt-cache state and rate limits on one color-coded line.
utility-tools
Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.
productivity
Standup reports, changelogs, and git productivity helpers.
mac-agent-hygiene
Keeps a Mac that runs Claude Code agents from filling its disk: a daily LaunchAgent plus an MCP server that clears regenerable caches (Xcode DerivedData, leftover plugin clones, browser-profile caches) and reaps stale git worktrees that are clean and already pushed. Plan first, apply on confirm.
pwdev-statusline
Configure and manage Claude Code status line — installs a rich, configurable bash status bar (single-jq-pass, dynamic colors, formatted tokens, truncated paths) showing model, git branch, context usage, rate limits, and token counts.
oat-publish-python
Python release management: cleanup, version bump, uv build, GitHub release, publish monitoring.