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.
npx agentmods add commands/ccplugins/awesome-claude-code-plugins/analyze-issuegit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWhat 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 | $0.00023 | $0.00205 |
| Opus 5 | $0.00012 | $0.00102 |
| Sonnet 5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
analyze-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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- analyze-issue — 100% identical, 0 lines differ
- analyze-issue — 100% identical, 0 lines differ
What it actually says
GitHub Issue Analysis and Technical Specification Generator
This template/script generates a technical specification for a GitHub issue with the following components:
Key Components
- A bash script to fetch GitHub issue details
- A structured technical specification template with sections:
- Issue Summary
- Problem Statement
- Technical Approach
- Implementation Plan
- Test Plan
- Files to Modify/Create
- Success Criteria
- Out of Scope
Principles
- Test-Driven Development (TDD)
- KISS (Keep It Simple, Stupid) approach
- 300-line file size limit
The template is designed to provide a comprehensive, structured approach to analyzing and documenting technical issues from GitHub.
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.
- 2d ago First seen · 29 lines · 23 tokens per session scan A 42183c07cad2
analyze-issue is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (926 stars, last pushed 20d ago), licensed Apache-2.0. It adds 23 tokens to every session and 205 once invoked, about $0.0001 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-30.
Other commands, from other repositories
e2e-test-command
This is a mock slash command file for E2E testing.
atl-fetch-confluence
Command "atl-fetch-confluence" from lc-semba-ryuichiro/semba-claude-plugins, covering confluence 情報取得コマンド, コマンド実行, オプション, 実行例 and ページ情報を取得（json）.
atl-fetch-jira
Command "atl-fetch-jira" from lc-semba-ryuichiro/semba-claude-plugins, covering jira 情報取得コマンド, コマンド実行, オプション, 実行例 and 課題情報を取得（json）.
webpify-list
WebPファイルの一覧と情報を表示.
webpify
画像ファイルを WebP 形式に変換.
diagram-drawio
Command "diagram-drawio" from lc-semba-ryuichiro/semba-claude-plugins, covering draw\.io図作成コマンド, 実行手順, スキル参照（必須） and 出力オプション.