agentmods.dev

katana-markdown-linter: Skill for Codex

.codex/skills/prepare-release-pr/SKILL.md

prepare-release-pr is a skill for Codex from HiroyukiFuruno/katana-markdown-linter. It costs 59 tokens per session (918 once invoked), scanned A, original, MIT.

A release-preparation skill that combines a pull request branch into one signed Git commit and can update the remote branch.

In plain words
What is it for?
Use it to prepare release/vX.Y.Z branches, create a GPG-signed commit, and optionally push the updated branch.
Why use it?
It prepares a release branch for merge checks that require a single verified commit, while checking branch names and repository state first.

Skill for Codex

Written for Codex: installed under .codex/.

This is HiroyukiFuruno/katana-markdown-linter's own configuration. It tells Codex how to work on katana-markdown-linter itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything katana-markdown-linter configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/hiroyuki_furuno/works/private/katana-markdown-linter.

not rated 0repo yesterday A scan 59 tokens original MIT
View source ↗ HiroyukiFuruno/katana-markdown-linter
Reuse

Borrowing it

Nothing to install: this file belongs to HiroyukiFuruno/katana-markdown-linter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/HiroyukiFuruno/katana-markdown-linter/master/.codex/skills/prepare-release-pr/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/HiroyukiFuruno/katana-markdown-linter

Made for: 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 prepare-release-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr/github.svg)](https://agentmods.dev/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr)
Your own site
<a href="https://agentmods.dev/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr"><img src="https://agentmods.dev/badge/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr/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 prepare-release-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr"><img src="https://agentmods.dev/badge/skills/hiroyukifuruno/katana-markdown-linter/prepare-release-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 918 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.00059 $0.00918
Opus 5.5 $0.00024 $0.00367
Sonnet 5.5 $0.00012 $0.00184
Haiku 4.5 $0.00006 $0.00092

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

Security

Grade A, and why

prepare-release-pr 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.

.codex/skills/prepare-release-pr/SKILL.md · 63 lines

What it actually says

PR署名前処理（準備）

このスキルは、/prepare-release-pr として呼び出します。
prepare-release-pr は PR 側の差分を main（既定）へ squash して1コミット化し、署名します。

実行する内容

  1. just prepare-release-pr を実行し、次をまとめて行う。
  2. リモートPRブランチを PR_BRANCH で受け取り、release/vX.Y.Z プレフィックスであることを確認して指定ベース(PR_BASE_BRANCH, 既定 main)へ git reset --soft する。
  3. 変更を gpg で1コミットにまとめる。
  4. git push --force-with-lease で対象PRブランチを更新する。

変数

  • PR_BRANCH（必須）
    • 例: origin/release/v0.18.0-7963409835081887532 か release/v0.18.0-7963409835081887532
    • release-v 系のブランチ名（例: origin/release-v0.18.0）は受け付けない。release/v0.18.0 に rename してから実行する。
  • PR_NUMBER（任意）
    • PR番号を直接与える（例: 85）
    • PR_BRANCH が未指定なら gh pr view でブランチ名を解決する
  • PR_REMOTE（任意）
    • 既定: origin
  • PR_BASE_BRANCH（任意）
    • 既定: main
  • PR_LOCAL_BRANCH（任意）
    • 既定: fix/<branch>-signed
  • PR_COMMIT_MESSAGE（任意）
    • 既定: Prepare release branch for merge checks
  • PR_NO_PUSH（任意）
    • 1 / true ならローカルコミットまでで終了し、push をしない。

事前チェック

  • git status --short がクリーンであること。
  • 対象PRブランチにコミット対象差分があること（差分が無ければ停止）。
  • GPGキー設定済みで git commit -S が通る環境であること。
  • PR ブランチ名が release/v で始まること。
    • origin/release-vX.Y.Z など別フォーマットは受理せず、先に release/vX.Y.Z に rename してから再実行する。

運用ルール（他のPR/Releaseに共通）

  • PRの更新はsquash + 署名1コミットに統一。
  • PR_NO_PUSH=1 で事前署名検証をしてから push する。
  • PR更新後は gh pr checks <PR> を確認してから merge。

実行コマンド

cd /Users/hiroyuki_furuno/works/private/katana-markdown-linter
git fetch --all --prune
git branch -m release-v0.18.0-7963409835081887532 release/v0.18.0-7963409835081887532
git push origin --delete release-v0.18.0-7963409835081887532
git push origin release/v0.18.0-7963409835081887532
PR_BRANCH=origin/release/v0.18.0-7963409835081887532 just prepare-release-pr
PR_NUMBER=85 just prepare-release-pr
PR_NUMBER=85 PR_NO_PUSH=1 just prepare-release-pr
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 · 63 lines · 59 tokens per session scan A 8a3348a02fac

Subscribe to this mod's changes

prepare-release-pr is a skill published in the GitHub repository HiroyukiFuruno/katana-markdown-linter (0 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 918 once invoked, about $0.0002 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.

Git and workflowReleases
Related

prepare-release-pr compared with skills from other repositories

prepare-release-pr next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
prepare-release-prHiroyukiFuruno/katana-markdown-linterSkill0yesterdayMITA59Codex
release-announcementpaperclipai/paperclipSkill111kyesterdayMITA42Claude Code, Codex
releasethedotmack/claude-memSkill114kyesterdayApache-2.0A13Claude Code
release-notesphuryn/pm-skillsSkill28k8d agoMITA57Claude Code
multi-agent-release-managerchromium/chromiumSkill25kyesterdayBSD-3-ClauseA27Claude Code, Codex
pack-submitaeonfun/aeonSkill788yesterdayMITA27Claude Code, Codex
updater_guidesiddsachar/row-botSkill1.7kyesterdayApache-2.0A22Claude Code, Codex