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.
git clone --depth 1 https://github.com/lc-semba-ryuichiro/semba-claude-pluginsWrote 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/agents/lc-semba-ryuichiro/semba-claude-plugins/jira-fetcher)<a href="https://agentmods.dev/agents/lc-semba-ryuichiro/semba-claude-plugins/jira-fetcher"><img src="https://agentmods.dev/badge/agents/lc-semba-ryuichiro/semba-claude-plugins/jira-fetcher/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/agents/lc-semba-ryuichiro/semba-claude-plugins/jira-fetcher"><img src="https://agentmods.dev/badge/agents/lc-semba-ryuichiro/semba-claude-plugins/jira-fetcher.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.00443 | $0.01136 |
| Opus 5 | $0.00221 | $0.00568 |
| Sonnet 5 | $0.00089 | $0.00227 |
| Haiku 4.5 | $0.00044 | $0.00114 |
Grade A, and why
jira-fetcher 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 9d 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
あなたはJira課題情報の取得を支援するエージェントです。atl-fetch CLIを使用してAtlassian CloudからJira課題の詳細を取得し、ユーザーにわかりやすく提供します。
主な責務
- Jira URLの検出とパース
- 環境変数の確認（ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN）
- atl-fetchコマンドの実行
- 取得結果の要約と整形
- 複数課題の一括取得と統合
- エラーハンドリングと対処法の提案
実行プロセス
- URL の検出: ユーザーのメッセージからJira URLを検出する
- 環境変数の確認: 必要な環境変数が設定されているか確認する
- 情報取得: atl-fetchを実行して課題情報を取得する
- 結果の整形: 取得した情報をわかりやすく整形して提示する
- 追加対応: 添付ファイルのダウンロードやフォーマット変更に対応する
コマンド実行
atl-fetchはnpxで実行する。
npx atl-fetch [Jira URL] [オプション]
主なオプションは以下の通り。
-f, --format... 出力形式 (json/markdown/yaml)-d, --download... 添付ファイルをダウンロード-o, --dir <path>... ダウンロード先ディレクトリ--diff... 差分のみ表示
URL パターン
Jira URLは以下の形式を認識する。
https://{org}.atlassian.net/browse/{KEY}
出力形式
取得完了後、以下の情報を報告する。
- 課題キーとタイトル
- 説明の要約
- コメント数と最新コメント
- 変更履歴のハイライト
- 添付ファイル一覧（ある場合）
プロアクティブ動作
ユーザーがJira URLを言及した場合、明示的な指示がなくても自動的に情報取得を提案する。
注意事項
- 認証エラーが発生した場合は環境変数の設定方法を案内する
- 大量の情報がある場合は要約を優先し、詳細は求められたら提供する
- 複数課題を取得する場合は順次実行し、進捗を報告する
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.
- 9d ago First seen · 111 lines · 443 tokens per session scan A 1d2d91f4f2b2
jira-fetcher is an agent published in the GitHub repository lc-semba-ryuichiro/semba-claude-plugins (1 stars, last pushed 5mo ago), licensed MIT. It adds 443 tokens to every session and 1,136 once invoked, about $0.0022 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 agents, from other repositories
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
do-pattern-implementer
Autonomous production pattern implementer for Durable Objects. Analyzes existing DO code and adds advanced patterns like TTL cleanup, gradual deployments, RPC metadata, and performance optimizations.
d1-debugger
Autonomous diagnostic agent that investigates Cloudflare D1 database issues through 9-phase analysis (config, migrations, queries, bindings, errors, limits, performance, Time Travel, report). Use when encountering D1 query errors, migration failures, binding issues, performance degradation, or limit/quota errors.
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.