A command that synchronizes a local cache of product-management requests with GitHub Issues, GitHub’s built-in system for tracking work and feedback.

Use it to fetch product-feature issues, create or update local request files, remove stale entries, record the sync time, and report a summary.

It helps keep local request files aligned with the corresponding GitHub issues, including newly created, changed, closed, or removed issues.

sync — Command for Claude Code by ooiyeefei/ccc

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ooiyeefei/ccc

Made for: Claude Code.

Or install product-management, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ooiyeefei/ccc/sync/github.svg)](https://agentmods.dev/commands/ooiyeefei/ccc/sync)

Your own site

<a href="https://agentmods.dev/commands/ooiyeefei/ccc/sync"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ooiyeefei/ccc/sync"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 406 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00007	$0.00406
Opus 5.5	$0.00003	$0.00162
Sonnet 5.5	$0.00001	$0.00081
Haiku 4.5	$0.00001	$0.00041

Measured 1mo ago against content hash d87379765eb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/product-management/commands/sync.md · 71 lines

What it actually says

GitHub Sync

Sync local .pm/requests/ cache with GitHub Issues for deduplication.

Prerequisites

Check GitHub CLI:

gh auth status

If not authenticated: "Run gh auth login first."

Process

Fetch All PM Issues

gh issue list --label "pm:feature-request" --state all --json number,title,body,labels,state,createdAt,updatedAt --limit 200

Create/Update Local Cache

Create .pm/requests/ directory if not exists
For each issue, create/update .pm/requests/[issue-number].md:

---
github_issue: [number]
title: "[title]"
state: [open/closed]
labels: [list]
created: [date]
updated: [date]
synced: [now]
---

[Issue body content]

Clean Up Stale Entries
- Remove local files for issues that no longer exist
- Update state for closed issues

Update Timestamp

Update .pm/cache/last-updated.json:

{
  "github_sync": "[ISO timestamp]",
  "issues_count": [N]
}

Report Summary

GitHub Sync Complete
- Issues synced: [N]
- New: [N]
- Updated: [N]
- Removed: [N]
- Last sync: [timestamp]

When to Run

Automatically suggested on session start if >24 hours since last sync
Before running /pm:gaps for accurate deduplication
After creating issues outside of PM plugin

Changes

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 First seen · 71 lines · 7 tokens per session scan A d87379765eb2

Subscribe to this mod's changes

sync is a command published in the GitHub repository ooiyeefei/ccc (496 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 406 once invoked, about $0.0000 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-30.

Git and workflow Project management

sync

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

GitHub Sync

Prerequisites

Process

When to Run

What this file has done since we first saw it

Other commands, from other repositories

project

land

standup

repo-architect

sync

claim