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-comment)<a href="https://agentmods.dev/skills/takashikakizoe1109/cc-backlog-connect/backlog-comment"><img src="https://agentmods.dev/badge/skills/takashikakizoe1109/cc-backlog-connect/backlog-comment/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-comment"><img src="https://agentmods.dev/badge/skills/takashikakizoe1109/cc-backlog-connect/backlog-comment.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.00126 | $0.00704 |
| Opus 5 | $0.00063 | $0.00352 |
| Sonnet 5 | $0.00025 | $0.00141 |
| Haiku 4.5 | $0.00013 | $0.00070 |
Grade A, and why
backlog-comment 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.
What it actually says
Backlog 課題のコメントを操作するスキルです。
事前チェック
まず .cc-backlog/config.json が存在するか確認してください。
存在しない場合は、操作を実行せず以下のように案内してください:
Backlog の接続設定がまだ行われていません。先に
/cc-backlog-connect:configを実行して設定してください。
実行方法
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment <subcommand> [options]
動作パターン
パターン1: コメント追加
ユーザーが「PROJ-123 にコメントして」と言った場合:
- コメント内容をユーザーに確認（すでに指定されている場合はそのまま使用）
- 実行:
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment add PROJ-123 --content "コメント内容" - 結果のURLを表示
重要: コメント内容は必ずユーザーに確認してから送信してください。勝手にコメントを作成しないでください。
パターン2: コメント一覧表示
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment list PROJ-123
JSON出力をユーザーに分かりやすく要約表示:
- 投稿者、日時、内容の一覧
パターン3: 特定コメント取得
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment get PROJ-123 --comment-id 456
パターン4: コメント更新
更新内容をユーザーに確認してから実行してください。
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment update PROJ-123 --comment-id 456 --content "更新内容"
パターン5: コメント削除
必ずユーザーに確認を取ってから実行してください。
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" comment delete PROJ-123 --comment-id 456
注意事項
- コメント内容にシェル特殊文字が含まれる場合は適切にエスケープしてください
- コメントの追加・更新・削除は常にユーザーの明示的な承認を得てから実行してください
詳細リファレンス
- 全サブコマンドの完全なオプション一覧、JSON出力構造は reference.md を参照
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 · 82 lines · 126 tokens per session scan A f1b5b738ed66
backlog-comment is a skill published in the GitHub repository TakashiKakizoe1109/cc-backlog-connect (2 stars, last pushed 6mo ago), licensed MIT. It adds 126 tokens to every session and 704 once invoked, about $0.0006 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…
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.
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".