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 syou6162/agent-skills --skill updating-pr-title-and-descriptiongit clone --depth 1 https://github.com/syou6162/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/syou6162/agent-skills/updating-pr-title-and-description)<a href="https://agentmods.dev/skills/syou6162/agent-skills/updating-pr-title-and-description"><img src="https://agentmods.dev/badge/skills/syou6162/agent-skills/updating-pr-title-and-description/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/syou6162/agent-skills/updating-pr-title-and-description"><img src="https://agentmods.dev/badge/skills/syou6162/agent-skills/updating-pr-title-and-description.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.00029 | $0.01539 |
| Opus 5 | $0.00015 | $0.00770 |
| Sonnet 5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
updating-pr-title-and-description 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Requestのタイトルと説明文を更新する
Pull Requestのタイトルと説明文を以下の手順で更新してください。
禁止事項
- 開発日誌（esa.io）のURLをPR descriptionに記載しない: 開発日誌はチーム内の作業記録であり、PRの説明文に含めるべきではない。
yasuhisa.esa.ioや esa.io ドメインのURLは関連情報セクションにも記載禁止
実行手順
-
デフォルトブランチの取得
デフォルトブランチを取得：
git symbolic-ref refs/remotes/origin/HEAD --short | cut -d/ -f2 -
修正内容の確認
デフォルトブランチからの差分を確認：
# <default-branch> には手順1で取得したブランチ名を使用 git diff <default-branch>...HEAD -
コミットメッセージの確認
デフォルトブランチからのコミット履歴を確認（本文も含む）：
# <default-branch> には手順1で取得したブランチ名を使用 git log <default-branch>..HEAD -
説明文ファイルの準備
.github/PULL_REQUEST_TEMPLATE.mdが存在する場合はコピー：cp .github/PULL_REQUEST_TEMPLATE.md .claude_work/pr_body_draft.md存在しない場合は新規ファイル作成：
touch .claude_work/pr_body_draft.md -
Pull Requestの説明文を作成
- 重要: 説明文を書く前に、必ず reference/description-rules.md を読み、そのルールに従うこと
- 作業ファイル（
.claude_work/pr_body_draft.md）を編集 - 上記で取得した情報とチャットの会話内容を考慮して説明文を作成
- 説明文は必ず日本語で記載すること
- 重要：ファイル編集には必ず
WriteツールまたはEditツールを使用すること - bashコマンド（
cat <<EOF > file、echo "..." > fileなど）でファイルを書き込んではいけません
5.5. CIチェックボックスの確認と記入（PR template使用時）
重要: PR templateにCIチェックボックスがある場合、PR作成/更新前に必ずCI状態を確認してチェックを記入すること。後からの確認は禁止。
a. CIチェックボックスの検出：
.claude_work/pr_body_draft.md内にCIチェックボックスがあるか確認：
grep -iE '- \[ \].*(CI|test|check|テスト)' .claude_work/pr_body_draft.md
b. PRが既に存在する場合のCI状態確認：
PRが存在するか確認し、存在する場合はCI状態を確認：
# PRが存在するか確認
if gh pr view >/dev/null 2>&1; then
# CI状態を確認
gh pr checks --json name,conclusion
fi
c. CI状態に基づくチェックボックスの記入：
- 全てのCIチェックが成功（
conclusion: SUCCESSまたはSKIPPED）している場合、Editツールでチェックを記入：- [ ] CI→- [x] CI- [ ] テスト→- [x] テスト- [ ] Tests pass→- [x] Tests pass
- 一部でも失敗またはペンディングの場合、チェックを入れない（
- [ ]のまま）
d. PRが新規作成の場合：
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.
- 12d ago First seen · 141 lines · 29 tokens per session scan A 3b7e3ef4be94
updating-pr-title-and-description is a skill published in the GitHub repository syou6162/agent-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,539 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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…