Borrowing it
Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. 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/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/biz:github-sync.mdgit clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplateWrote 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/reinhardhq/claude-code-spec-boilerplate/biz-github-sync)<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-github-sync"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-github-sync.svg" alt="Measured on agentmods" 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.00022 | $0.02644 |
| Opus 5 | $0.00011 | $0.01322 |
| Sonnet 5 | $0.00004 | $0.00529 |
| Haiku 4.5 | $0.00002 | $0.00264 |
Grade B, and why
biz:github-sync scanned grade B with 2 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo gpg --dearmor -o /usr/share/keyrings/githubcli-archive-keyring.gpg Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo gpg --dearmor -o /usr/share/keyrings/githubcli-archive-keyring.gpg How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Task Synchronizer
タスクリストをGitHub Issues化し、Project boardsやMilestonesと連携して、チーム開発を円滑に進めるためのツールです。
入力パラメータ:
- リポジトリ: $REPO (owner/repo形式)
- タスクリスト: $TASKS
Environment Check
GitHub CLI Status
- CLI確認: !
which gh && gh --version || echo "GitHub CLI not installed" - 認証状態: !
gh auth status 2>&1 || echo "Not authenticated" - リポジトリ確認: !
[ -d .git ] && git remote -v | grep origin || echo "No git repository"
Task: GitHub同期の実行
1. タスクリストの解析
A. タスク形式の理解
入力されたタスクリストから以下を抽出：
- タスク名: Issue titleとして使用
- カテゴリ: Labelとして使用
- 優先度: Priority labelとして使用
- 担当者: Assigneeとして使用
- 見積時間: Project fieldとして使用
- 依存関係: Issue本文に記載
B. GitHub要素へのマッピング
- タスク → Issue
- カテゴリ → Label
- マイルストーン → Milestone
- 依存関係 → Issue links
- 見積もり → Custom fields
2. Issue作成の準備
A. Label管理
必要なLabel:
カテゴリ:
- backend
- frontend
- infrastructure
- design
- testing
- documentation
優先度:
- P0-critical
- P1-high
- P2-medium
- P3-low
ステータス:
- todo
- in-progress
- review
- done
B. Milestone設定
- スプリント/イテレーション単位
- リリースバージョン単位
- 四半期目標単位
C. Project Board設定
- カンバンボード形式
- 自動化ルールの設定
- カスタムフィールドの定義
3. Issue テンプレートの生成
A. Issue本文の構造
- 概要: タスクの目的と背景
- 詳細: 実装内容の具体的説明
- 受入条件: Definition of Done
- 技術仕様: 必要に応じた技術詳細
- 依存関係: 他のIssueとの関連
- 参考資料: 関連ドキュメントへのリンク
B. メタデータの付与
- Labels
- Assignees
- Milestone
- Projects
- Estimate (custom field)
4. 自動化スクリプトの生成
A. Bash スクリプト生成
- gh CLIを使用したIssue作成
- 一括作成用のループ処理
- エラーハンドリング
- 進捗レポート
B. GitHub Actions設定
- Issue作成時の自動化
- ステータス更新の連携
- 通知設定
5. チーム連携の最適化
A. 通知設定
- Slackとの連携
- メール通知のカスタマイズ
- Webhook設定
B. レポーティング
- 進捗ダッシュボード
- バーンダウンチャート
- ベロシティ追跡
Output: GitHub同期設定
🔗 GitHub Issue 同期設定
Repository: $REPO Total Tasks: [タスク総数] Estimated Total Hours: [総見積時間]
📋 タスク一覧と Issue マッピング
| Task | Category | Priority | Assignee | Hours | Issue Template |
|---|---|---|---|---|---|
| [タスク1] | backend | P0 | @dev1 | 16h | See below |
| [タスク2] | frontend | P1 | @dev2 | 8h | See below |
| ... | ... | ... | ... | ... | ... |
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.
- 6d ago First seen · 375 lines · 22 tokens per session scan B 76c7a5596549
biz:github-sync is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 22 tokens to every session and 2,644 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.