Borrowing it
Nothing to install: this file belongs to suisya-systems/claude-org-ja. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/suisya-systems/claude-org-ja/main/.claude/skills/runtime-release-with-paired-ja-sync/SKILL.mdgit clone --depth 1 https://github.com/suisya-systems/claude-org-jaWrote 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/suisya-systems/claude-org-ja/runtime-release-with-paired-ja-sync)<a href="https://agentmods.dev/skills/suisya-systems/claude-org-ja/runtime-release-with-paired-ja-sync"><img src="https://agentmods.dev/badge/skills/suisya-systems/claude-org-ja/runtime-release-with-paired-ja-sync/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/suisya-systems/claude-org-ja/runtime-release-with-paired-ja-sync"><img src="https://agentmods.dev/badge/skills/suisya-systems/claude-org-ja/runtime-release-with-paired-ja-sync.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.00142 | $0.07429 |
| Opus 5 | $0.00071 | $0.03714 |
| Sonnet 5 | $0.00028 | $0.01486 |
| Haiku 4.5 | $0.00014 | $0.00743 |
Grade B, and why
runtime-release-with-paired-ja-sync scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
settings（`~/.claude/settings.json` 等）は CI 対象外。CI green でも local は stale に How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
runtime-release-with-paired-ja-sync: runtime リリース＋ja-side 同期ワークフロー
claude-org-runtime のリリースは PyPI 発行を経由して claude-org-ja の attention watcher integration test に必ず波及する。 本 skill はそのカスケードを「リリース起票時に予測し、paired ja-sync を同一 Secretary セッション内で land しきる」ためのチェックリスト。
本 SKILL のスコープ: 窓口が runtime release 系タスクを受領した際の 委譲設計と paired ja-sync 計画。実 commit / テスト修正はワーカー側であり本 skill ではない。
なぜこの skill が必要か
claude-org-runtime 側で DEFAULT_NOTIFY の値や classifier 語彙・role_configs_schema.json
（runtime 同梱 schema。ja 側ミラーが tools/org_extension_schema.json）の項目を
更新してリリースすると、PyPI publish 後に claude-org-ja 側の以下が同時に古くなる:
tests/test_attention_runtime_integration.pyの expectationtools/org_extension_schema.jsonのバイト一致コピー.claude/skills/org-setup/references/permissions.mdの projectiontools/templates/attention.example.jsonの severity / TTL
過去のリリースサイクルでは「runtime release は無事だったが ja-side CI が翌日に red」になる カスケードが観測されており、これを毎回観測してから後追いで直すと、
- Secretary セッションが切れて context を失う
- ja-side worker に「なぜこの変更が必要か」の経路を再構築させる
- 修正の paired-ness が暗黙的になり次回も同じカスケードを踏む
の 3 重コストが発生する。本 skill は paired-ness をリリース起票時に明示化し、 同一 Secretary セッション内で land しきる規律を提供する。
発動条件
以下のいずれかに該当する場合、Secretary は org-delegate より前にこの skill を確認する:
- task_id に
releaseを含む、またはvX.Y.Z形式のタグを発行するリリース系タスク - chore release 系のユーザー指示プロンプト（「runtime のリリース」「PyPI 上げ」等）
- runtime 側の
DEFAULT_NOTIFY/ classifier mapping /role_configs_schema.json/ attention テンプレのいずれかを触る変更が land 寸前 - runtime 側の
role_configs_schema.jsonにあるrequired_allow/required_deny/required_hook_scripts/required_hooksへの追加・変更を含むリリース。 これらは「settings ファイルに必ず存在すべき項目」を増やす変更であり、runtime 側 CI が full green・Codex 指摘ゼロでも ja 側の安全性は証明されない。ja は floating pin （>=X,<0.2）のため PyPI 公開の瞬間から ja 側の 2 系統のチェックが赤くなる: (a)tools/check_role_configs.py— permissions projection と tracked settings を schema との整合で検証する。CI 配線は--include-worker-settings（.github/workflows/tests.yml）で、machine-local settings（~/.claude/settings.json等）は CI 対象外。CI green でも local は stale に なり得るため、merge 後に/org-setupで反映する。なお--include-localは schema にsettings_pathsが宣言された role の settings.local.json しか見ず（user_commonはsettings_paths: []）、参照 schema も checked-in の ja ミラーなので、home レベル （~/.claude/settings.json）の allowlist 検証ゲートにはならない — user_common の 現物反映は/org-setup適用後に settings 現物を直接確認する。 (b)tools/check_runtime_schema_drift.py— ja のtools/org_extension_schema.jsonと runtime 同梱role_configs_schema.jsonの、ja 固有節を strip した上でのバイト比較 （CI で実行。installed runtime が pin window 内なら skip されない）。 実例: renga capability probeserver_infoのrequired_allow追加 （2026-08-08, runtime Issue #161）で露見
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.
- 6d ago Changed · +17 lines 45142ba12d5c
- 11d ago First seen · 356 lines · 142 tokens per session scan B 512ec2796994
runtime-release-with-paired-ja-sync is a skill published in the GitHub repository suisya-systems/claude-org-ja (5 stars, last pushed 5d ago), licensed MIT. It adds 142 tokens to every session and 7,429 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
b3os-release-ops
A release and deployment checklist for the b3os project. It covers merging code, live releases, urgent fixes, and changes to public Git history.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.