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/commands/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira)<a href="https://agentmods.dev/commands/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira"><img src="https://agentmods.dev/badge/commands/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira/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/commands/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira"><img src="https://agentmods.dev/badge/commands/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira.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.00013 | $0.00518 |
| Opus 5 | $0.00006 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
atl-fetch-jira 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
Jira 情報取得コマンド
jira-fetcherサブエージェントを使用して、Jira課題情報を取得してください。
引数: $ARGUMENTS
コマンド実行
atl-fetchはnpxで実行する。
npx atl-fetch [Jira URL] [オプション]
オプション
| オプション | 説明 |
|---|---|
-f, --format |
出力形式 (json/markdown/yaml) |
-d, --download |
添付ファイルをダウンロード |
-o, --dir <path> |
ダウンロード先ディレクトリ（--download 必須） |
--diff |
差分のみ表示 |
-v, --verbose |
詳細出力を有効化 |
--debug |
デバッグ出力を有効化（開発者向け） |
実行例
# 課題情報を取得（JSON）
npx atl-fetch https://example.atlassian.net/browse/PROJ-123
# Markdown 形式で取得
npx atl-fetch https://example.atlassian.net/browse/PROJ-123 -f markdown
# 添付ファイルをダウンロード
npx atl-fetch https://example.atlassian.net/browse/PROJ-123 -d -o ./downloads
# 差分のみ表示
npx atl-fetch https://example.atlassian.net/browse/PROJ-123 --diff
事前確認
実行前に以下の環境変数が設定されているか確認する。
ATLASSIAN_EMAILATLASSIAN_API_TOKEN
注意事項
- 対象のJiraプロジェクトへのアクセス権が必要
- URLは
https://{org}.atlassian.net/browse/{KEY}形式で指定 - 認証エラーが発生した場合は環境変数を確認する
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 · 63 lines · 13 tokens per session scan A 27485a3c6a84
atl-fetch-jira is a command published in the GitHub repository lc-semba-ryuichiro/semba-claude-plugins (1 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 518 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-31.
Other commands, from other repositories
sync
Manually trigger todo sync to Fizzy.do.
status
Show Fizzy.do connection and sync status.
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:migrate
Interactive Durable Objects migration assistant. Guides through new class creation, renaming, deletion, and transfer migrations with validation.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
cloudflare-durable-objects:patterns
Interactive Durable Objects pattern selection wizard. Helps choose the right DO pattern for your use case and generates implementation code with best practices.