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 skills/eaglesakura/agent-skills/github-resolve-url-metadatanpx skills add eaglesakura/agent-skills --skill github-resolve-url-metadatagit clone --depth 1 https://github.com/eaglesakura/agent-skillsWrote 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/eaglesakura/agent-skills/github-resolve-url-metadata)<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="Measured on agentmods" 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 | $0.00154 | $0.01130 |
| Opus 5 | $0.00077 | $0.00565 |
| Sonnet 5 | $0.00031 | $0.00226 |
| Haiku 4.5 | $0.00015 | $0.00113 |
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 5d 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
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 行の文字列 |
作業手順
- URL の種別（ホスト／サービス）を判別する
- サポート済みなら対応手順で取得する。未サポートなら取得手段を調べ、同じメタデータ項目へ写す
- タスクID・タイトルへマッピングする
#などの装飾を付けず、生の値として渡す
サポート済み 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
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.
- 5d ago First seen · 83 lines · 154 tokens per session scan A 7921de7e8939
github-resolve-url-metadata is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed today), licensed MIT. It adds 154 tokens to every session and 1,130 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…