Borrowing it
Nothing to install: this file belongs to tarunkorat/claude-linkedin-post-creator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tarunkorat/claude-linkedin-post-creator/main/.claude/commands/post/sync.mdgit clone --depth 1 https://github.com/tarunkorat/claude-linkedin-post-creatorWrote 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/commands/tarunkorat/claude-linkedin-post-creator/sync)<a href="https://agentmods.dev/commands/tarunkorat/claude-linkedin-post-creator/sync"><img src="https://agentmods.dev/badge/commands/tarunkorat/claude-linkedin-post-creator/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/commands/tarunkorat/claude-linkedin-post-creator/sync"><img src="https://agentmods.dev/badge/commands/tarunkorat/claude-linkedin-post-creator/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.00000 | $0.00395 |
| Opus 5.5 | $0.00000 | $0.00158 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
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 2mo 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
SYNC — Pull profile from LinkedIn into config/profile.md
Run once on setup. Re-run when your focus or style changes.
Step 1
Run Step 0B and 0C from _shared.md (skip 0A profile check — that's what we're fixing).
Print: Syncing from LinkedIn...
Step 2 — Read profile page
Navigate to https://www.linkedin.com/in/me/. Read page text.
Extract: full name, headline, about section (click "see more" if collapsed), current company/title, location.
Step 3 — Read recent posts
Navigate to https://www.linkedin.com/in/me/recent-activity/shares/. Read page.
Extract last 5 posts: full text + reaction/comment counts if visible.
Step 4 — Analyze style (internal, don't show user)
From the 5 posts, note: avg word count, tone, format patterns, hook types, emoji usage, hashtag count/style, recurring topics, highest-engagement post.
Step 5 — Write config/profile.md
Read current config/profile.md. Fill in or update:
- NAME, ROLE (from headline), INDUSTRY (infer from about + posts), EXPERIENCE_YEARS (estimate)
- NICHE_TOPICS (from recurring post topics + about section)
- TONE, FORMAT, VOICE (from Step 4 analysis)
- SAMPLE_1, SAMPLE_2, SAMPLE_3 (3 best posts — highest engagement, or most recent)
Preserve any fields the user already filled in. Only overwrite empty or placeholder fields.
Step 6 — Confirm
Print a short summary:
✓ Synced
Updated: NAME, ROLE, NICHE_TOPICS, style fields, 3 post samples
Kept: <any fields already filled>
Review config/profile.md if anything looks off.
Run /post to generate your first post.
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.
- 2mo ago First seen · 40 lines · 0 tokens per session scan A 533a591d0882
sync is a command published in the GitHub repository tarunkorat/claude-linkedin-post-creator (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 395 tokens. 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 commands, from other repositories
content-pipeline
Run the full multi-agent content production pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.