Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TakashiKakizoe1109/cc-backlog-connect/plugin install cc-backlog-connectWrote 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/skills/takashikakizoe1109/cc-backlog-connect/backlog-issue)<a href="https://agentmods.dev/skills/takashikakizoe1109/cc-backlog-connect/backlog-issue"><img src="https://agentmods.dev/badge/skills/takashikakizoe1109/cc-backlog-connect/backlog-issue/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/skills/takashikakizoe1109/cc-backlog-connect/backlog-issue"><img src="https://agentmods.dev/badge/skills/takashikakizoe1109/cc-backlog-connect/backlog-issue.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.00225 | $0.02310 |
| Opus 5 | $0.00112 | $0.01155 |
| Sonnet 5 | $0.00045 | $0.00462 |
| Haiku 4.5 | $0.00022 | $0.00231 |
Grade A, and why
backlog-issue 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog の課題を操作するスキルです。
事前チェック
まず .cc-backlog/config.json が存在するか確認してください。
存在しない場合は、操作を実行せず以下のように案内してください:
Backlog の接続設定がまだ行われていません。先に
/cc-backlog-connect:configを実行して設定してください。
実行方法
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue <subcommand> [options]
動作パターン
パターン1: 課題キー検出 → 情報取得
ユーザーが課題キー（例: PROJ-123）に言及した場合:
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue get PROJ-123を実行- 取得した JSON を以下の形式で要約表示:
- 課題キー、タイトル、ステータス、担当者、優先度
- 説明文（長い場合は要約）
- URL
パターン2: 課題の更新（キャッシュ利用の高速パターン）
ユーザーが「ステータスを変更して」「担当者を変えて」等と言った場合:
キャッシュがある場合（推奨）: 名前ベースフラグを直接使用（API往復が不要）
# ステータスを名前で指定（キャッシュから解決）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --status "完了"
# 担当者を名前で指定
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --assignee "山田太郎"
# 優先度を名前で指定
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --priority "高"
# 種別を名前で指定
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --type "バグ"
キャッシュがない場合: project-info でメタデータを取得してIDを解決
# 1. ステータス一覧取得（キャッシュに保存される）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" project-info statuses
# → [{"id": 4, "name": "完了"}, ...]
# 2. 更新実行（ID指定）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --status-id 4
例: 「PROJ-123 のステータスを完了にして」
# キャッシュがあれば1コマンドで完了
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue update PROJ-123 --status "完了"
パターン3: 課題の新規作成
ユーザーが「課題を作って」「Backlogにチケット登録して」等と言った場合:
キャッシュを使う場合（名前指定）:
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue create --summary "タイトル" --type "タスク" --priority "中"
ID指定の場合:
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue create --summary "タイトル" --type-id <id> --priority-id <id>
キャッシュがない場合は先に project-info issue-types と project-info priorities を実行してください。
パターン4: 課題の検索・フィルタリング
# キーワード検索
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --keyword "バグ"
# ステータス指定（名前またはID）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --status "完了"
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --status-id 1,2
# 担当者で絞り込み（名前・userIdまたはID）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --assignee "山田太郎"
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --assignee "yamada"
# 種別で絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --type "バグ"
# カテゴリーで絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --category "バックエンド"
# マイルストーンで絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --milestone "v1.0"
# 発生バージョンで絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --version "v1.0"
# 優先度で絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --priority "高"
# 登録者で絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --created-user "山田太郎"
# 完了理由で絞り込み
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --resolution "対応済み"
# 親課題のみ絞り込み（0=全て 1=子課題以外 2=子課題のみ 3=どちらでもない 4=親課題のみ）
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue search --parent-child 4
# 課題数取得
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" issue count --status "完了"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 199 lines · 225 tokens per session scan A 6469d362141b
backlog-issue is a skill published in the GitHub repository TakashiKakizoe1109/cc-backlog-connect (2 stars, last pushed 6mo ago), licensed MIT. It adds 225 tokens to every session and 2,310 once invoked, about $0.0011 per session on Opus 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-31.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
handover-admin
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".
Product Strategy
A comprehensive skill for product strategy — covering frameworks, opportunity sizing, prioritization, roadmap building, OKRs, and stakeholder management. From early-stage discovery to mature product org execution.