scopes: Command for Claude Code

.claude/commands/pm/sync.md

sync is a command for Claude Code from kamiazya/scopes. It costs 0 tokens per session (504 once invoked), scanned A, original, Apache-2.0.

A two-way synchronization command between local project-management files and GitHub issues, where GitHub is a service for tracking software work.

In plain words
What is it for?
Use it to pull updated issues into local files, create or update GitHub issues from local tasks, and synchronize one project group or all groups.
Why use it?
It keeps task status and content aligned in both places and identifies conflicts when both versions changed.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is kamiazya/scopes's own configuration. It tells Claude Code how to work on scopes itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything scopes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kamiazya/scopes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kamiazya/scopes/main/.claude/commands/pm/sync.md
Clone the repo
git clone --depth 1 https://github.com/kamiazya/scopes

Made for: Claude Code.

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.

agentmods badge for sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/kamiazya/scopes/sync/github.svg)](https://agentmods.dev/commands/kamiazya/scopes/sync)
Your own site
<a href="https://agentmods.dev/commands/kamiazya/scopes/sync"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/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.

agentmods 80×15 button for sync

Your own site · 80×15
<a href="https://agentmods.dev/commands/kamiazya/scopes/sync"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 504 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00504
Opus 5.5 $0.00000 $0.00202
Sonnet 5.5 $0.00000 $0.00101
Haiku 4.5 $0.00000 $0.00050

Measured 2mo ago against content hash 2799ad79df2d, 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 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.

.claude/commands/pm/sync.md · 83 lines

What it actually says

Sync

Full bidirectional sync between local and GitHub.

Usage

/pm:sync [epic_name]

If epic_name provided, sync only that epic. Otherwise sync all.

Instructions

1. Pull from GitHub

Get current state of all issues:

# Get all epic and task issues
gh issue list --label "epic" --limit 1000 --json number,title,state,body,labels,updatedAt
gh issue list --label "task" --limit 1000 --json number,title,state,body,labels,updatedAt

2. Update Local from GitHub

For each GitHub issue:

  • Find corresponding local file by issue number
  • Compare states:
    • If GitHub state newer (updatedAt > local updated), update local
    • If GitHub closed but local open, close local
    • If GitHub reopened but local closed, reopen local
  • Update frontmatter to match GitHub state

3. Push Local to GitHub

For each local task/epic:

  • If has GitHub URL but GitHub issue not found, it was deleted - mark local as archived
  • If no GitHub URL, create new issue (like epic-sync)
  • If local updated > GitHub updatedAt, push changes:
    gh issue edit {number} --body-file {local_file}
    

4. Handle Conflicts

If both changed (local and GitHub updated since last sync):

  • Show both versions
  • Ask user: "Local and GitHub both changed. Keep: (local/github/merge)?"
  • Apply user's choice

5. Update Sync Timestamps

Update all synced files with last_sync timestamp.

6. Output

🔄 Sync Complete

Pulled from GitHub:
  Updated: {count} files
  Closed: {count} issues
  
Pushed to GitHub:
  Updated: {count} issues
  Created: {count} new issues
  
Conflicts resolved: {count}

Status:
  ✅ All files synced
  {or list any sync failures}

Important Notes

Follow /rules/github-operations.md for GitHub commands. Follow /rules/frontmatter-operations.md for local updates. Always backup before sync in case of issues.

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.

  1. 2mo ago First seen · 83 lines · 0 tokens per session scan A 2799ad79df2d

Subscribe to this mod's changes

sync is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 11mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 504 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.

Related

sync compared with commands from other repositories

sync next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
synckamiazya/scopesCommand211mo agoApache-2.0A0Claude Code
CHANGELOGbytedance/UI-TARS-desktopCommand40k29d agoApache-2.0A0Claude Code
diagnose-deeptracezscaler/zscaler-mcp-serverCommand5510d agoMITA29Claude Code
create-access-rulezscaler/zscaler-mcp-serverCommand5510d agoMITA20Claude Code
investigate-incidentzscaler/zscaler-mcp-serverCommand5510d agoMITA27Claude Code
review-attack-surfacezscaler/zscaler-mcp-serverCommand5510d agoMITA27Claude Code
create-timeout-rulezscaler/zscaler-mcp-serverCommand5510d agoMITA21Claude Code