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 skills add lc-semba-ryuichiro/semba-claude-plugins --skill atl-fetch-jiragit 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/skills/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira)<a href="https://agentmods.dev/skills/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira"><img src="https://agentmods.dev/badge/skills/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/skills/lc-semba-ryuichiro/semba-claude-plugins/atl-fetch-jira"><img src="https://agentmods.dev/badge/skills/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.00083 | $0.01530 |
| Opus 5 | $0.00042 | $0.00765 |
| Sonnet 5 | $0.00017 | $0.00306 |
| Haiku 4.5 | $0.00008 | $0.00153 |
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 11d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira 情報取得ガイド
目次
概要
atl-fetchはAtlassian CloudからJira課題情報を取得するCLIツール。課題の詳細、コメント、変更履歴、添付ファイルを一括で取得できる。
事前準備チェックリスト
取得する前に確認する。
- 環境変数
ATLASSIAN_EMAILが設定されているか - 環境変数
ATLASSIAN_API_TOKENが設定されているか - 対象のJiraプロジェクトへのアクセス権があるか
- Node.jsがインストールされているか
実行方法
atl-fetchはnpxで都度実行する。グローバルインストールは不要。
npx atl-fetch [Jira URL] [オプション]
CLI オプション一覧
| オプション | 説明 | デフォルト |
|---|---|---|
-f, --format |
出力形式 (json/markdown/yaml) | json |
-d, --download |
添付ファイルをダウンロード | false |
-o, --dir <path> |
ダウンロード先ディレクトリ（--download 必須） |
- |
--diff |
差分のみ表示 | false |
--color |
カラー出力有効 | true |
--no-color |
カラー出力無効 | false |
-v, --verbose |
詳細出力を有効化 | false |
--debug |
デバッグ出力を有効化（開発者向け） | false |
認証情報の確認
認証情報が正しく設定されているか確認する。
npx atl-fetch auth check
URL フォーマット
Jira課題URLは以下の形式で指定する。
https://{org}.atlassian.net/browse/{KEY}
例:
https://mycompany.atlassian.net/browse/PROJ-123https://example.atlassian.net/browse/DEV-456
よくある使用パターン
課題情報を JSON で取得
npx atl-fetch https://mycompany.atlassian.net/browse/PROJ-123
Markdown 形式で取得
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.
- 11d ago First seen · 188 lines · 83 tokens per session scan A e6b226ec2126
atl-fetch-jira is a skill published in the GitHub repository lc-semba-ryuichiro/semba-claude-plugins (1 stars, last pushed 5mo ago), licensed MIT. It adds 83 tokens to every session and 1,530 once invoked, about $0.0004 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
fizzy-workflow
Use for guided Fizzy.do workflows: "set up Fizzy", "configure Fizzy for this project", "sync my work to Fizzy", "review my Fizzy progress", "end of session cleanup". Provides step-by-step guidance for common operations.
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-cron-triggers
Cloudflare Cron Triggers for scheduled Workers execution. Use for periodic tasks, scheduled jobs, or encountering handler not found, invalid cron expression, timezone errors.
cloudflare-durable-objects
Cloudflare Durable Objects for stateful coordination and real-time apps. Use for chat, multiplayer games, WebSocket hibernation, or encountering class export, migration, alarm errors.
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker…
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.