agentmods.dev

github-resolve-url-metadata

github-resolve-url-metadata is a skill for Claude Code, Codex from eaglesakura/agent-skills. It costs 154 tokens per session (1,130 once invoked), scanned A, original, MIT.

A URL-to-details resolver for tasks, tickets, and pages. For supported links such as GitHub issue URLs, it retrieves the real task number and title instead of guessing from the address.

In plain words
What is it for?
Use it to read the ID and title from GitHub issue links and to normalize task or page links before implementation, review, or documentation work.
Why use it?
It turns a link into consistent information that other work can use. This avoids mistakes caused by relying on branch names, URL text, or assumptions about the task.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 2repo 1mo ago A scan 154 tokens original MIT

Good fit Use it to read the ID and title from GitHub issue links and to normalize task or page links before implementation, review, or documentation work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eaglesakura/agent-skills/github-resolve-url-metadata
View source ↗ eaglesakura/agent-skills
Install

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.

Any agent
npx skills add eaglesakura/agent-skills --skill github-resolve-url-metadata
Clone the repo
git clone --depth 1 https://github.com/eaglesakura/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for github-resolve-url-metadata

README.md
[![agentmods](https://agentmods.dev/badge/skills/eaglesakura/agent-skills/github-resolve-url-metadata/github.svg)](https://agentmods.dev/skills/eaglesakura/agent-skills/github-resolve-url-metadata)
Your own site
<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/github-resolve-url-metadata"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/github-resolve-url-metadata/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.

agentmods 80×15 button for github-resolve-url-metadata

Your own site · 80×15
<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/github-resolve-url-metadata"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/github-resolve-url-metadata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00154 $0.01130
Opus 5.5 $0.00062 $0.00452
Sonnet 5.5 $0.00031 $0.00226
Haiku 4.5 $0.00015 $0.00113

Measured 2mo ago against content hash 7921de7e8939, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-resolve-url-metadata 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 2mo 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.

packages/github/.apm/skills/github-resolve-url-metadata/SKILL.md · 83 lines

What it actually says

GitHub / Resolve URL Metadata

タスクやチケット、ページを指す URL から、後続作業で使うメタデータ（主にタスクID・タイトル）を取得する。 推測で埋めず、可能な限り各サービスの API / CLI 等で実データを取る。 対応ホストは増える想定（現状の具体手順は下記のサポート済み URL。未記載の URL は種別を判別したうえで取得手段を調べ、同じメタデータ項目へマッピングする）。

いつ使うか

  • 貼られた URL からタスクID／タイトルを取るとき（GitHub Issue、将来の Notion 等を含む）
  • 「この URL のタスクID / タイトルは？」と聞かれたとき
  • ドキュメントやチャットのチケット／ページ URL を作業入力に正規化するとき

いつ使わないか

  • ブランチ名 feature/id/{n}/... から Issue を辿るだけ（ブランチ規約向けの SKILL がある場合はそちら。必要なら本 SKILL と併用可）
  • PR レビュー・CI 失敗調査そのもの（URL パースが必要なら入口だけ本 SKILL）
  • ローカルファイルパスの解決（本 SKILL の範囲外）

メタデータ一覧

項目 意味
タスクID タスクを一意に識別する ID。同一空間（例: 同一リポジトリ）内では重複しないが、空間横断では重複しうる
タイトル タスク内容を表す 1 行の文字列

作業手順

  1. URL の種別（ホスト／サービス）を判別する
  2. サポート済みなら対応手順で取得する。未サポートなら取得手段を調べ、同じメタデータ項目へ写す
  3. タスクID・タイトルへマッピングする
  4. # などの装飾を付けず、生の値として渡す

サポート済み URL

https://github.com/{オーナー}/{リポジトリ名}/issues/{Issue番号}

gh issue view {Issue番号} --repo {オーナー}/{リポジトリ名} --json number,title

{
  "number": 261,
  "title": "（実際のIssueタイトル）"
}
  • タスクID … number を使う。# 等の Prefix を含めず、単純な数値
  • タイトル … title を使う

URL から {オーナー} / {リポジトリ名} / {Issue番号} を読み取り、プレースホルダを置き換える。 GitHub では owner/repo を --repo で明示する（カレントのデフォルト repo に頼らない）。

ナレッジベース

DO: まず URL 種別を判別し、サービス固有の取得手段で実データを取る

  • ホストが違えばコマンドも違う。共通なのは「ID とタイトルへの正規化」

DO: タスクID は装飾なしの生の値（GitHub Issue なら #261 にせず 261）

  • 後続のブランチ名やスクリプト入力と揃えやすくするため

DO NOT: タイトルや ID を URL 断片から推測して確定扱いする

  • API / CLI が取れるなら実データを優先する（取れないときだけ推測と明示する）

DO NOT: ブランチ命名ルールの説明だけでチケット中身の取得を済ませようとする

  • ブランチ解釈はブランチ規約向け SKILL、URL→メタデータは本 SKILL
Files

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.

Changes

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.

  1. 2mo ago First seen · 83 lines · 154 tokens per session scan A 7921de7e8939

Subscribe to this mod's changes

github-resolve-url-metadata is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 154 tokens to every session and 1,130 once invoked, about $0.0006 per session on Opus 5.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.

Project management
Related

github-resolve-url-metadata compared with skills from other repositories

github-resolve-url-metadata next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
github-resolve-url-metadataeaglesakura/agent-skillsSkill21mo agoMITA154Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex