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 j5ik2o/okite-ai --skill pr-greengit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/pr-green)<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/pr-green"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/pr-green/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/j5ik2o/okite-ai/pr-green"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/pr-green.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.00271 | $0.01815 |
| Opus 5 | $0.00135 | $0.00907 |
| Sonnet 5 | $0.00054 | $0.00363 |
| Haiku 4.5 | $0.00027 | $0.00181 |
Grade A, and why
pr-green 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 7d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Green スキル
PR の CI チェック失敗と紐づく Issue を解消し、PR をマージ可能な状態にする。
動作モード
| モード | 起動方法 | 振る舞い |
|---|---|---|
| 対話モード | /pr-green or 「CI を直して」 |
状況報告→ユーザー確認→修正→確認→プッシュ |
| ループモード | /loop 5 /pr-green |
自律的に監視・修正・コミット・プッシュ。問題なければ即終了 |
/loop 経由で呼ばれた場合はループモードとして動作する。判断がつかない場合は対話モードとする。
モード別の振る舞いの違い
| 判断ポイント | 対話モード | ループモード |
|---|---|---|
| 状況サマリー | 詳細に表示し確認を取る | 問題がある場合のみ簡潔に表示 |
| 修正前の確認 | ユーザーに方針確認 | 確認なしで修正を開始 |
| コミット・プッシュ | ユーザー確認後 | 自動 |
| Issue クローズ | 一覧提示→承認後クローズ | 自動クローズ（コメント付き） |
| 問題なしの場合 | 「すべてグリーンです」と報告 | 何も出力せず即終了 |
| 結果報告 | 詳細な修正レポート | 修正した場合のみ簡潔に報告 |
| 判断困難な問題 | ユーザーに相談 | スキップして報告 |
ワークフロー
ステップ 0: PR の特定
引数で PR 番号が指定されていればそれを使う。指定がなければ現在のブランチから自動検出する。
gh pr view --json number,title,state,statusCheckRollup,url,headRefName
PR が見つからない場合は報告して終了する。
ステップ 1: 状況の把握
1a. CI チェックの状態確認
gh pr checks <number>
# 失敗した CI の詳細ログ（run-id は checks 結果から特定）
gh run view <run-id> --log-failed
1b. PR に紐づく Issue の確認
PR レビューコメント（CodeRabbit 等のボットレビュー含む）：
gh api repos/{owner}/{repo}/pulls/<number>/reviews --jq '.[] | select(.state != "APPROVED") | {user: .user.login, state: .state, body: .body}'
gh api repos/{owner}/{repo}/pulls/<number>/comments --jq '.[] | {user: .user.login, body: .body, path: .path, line: .line, created_at: .created_at}'
PR にリンクされた Issue：
gh pr view <number> --json closingIssuesReferences --jq '.closingIssuesReferences[] | {number, title}'
1c. 早期終了判定（ループモード）
以下の条件をすべて満たす場合は何もせず即終了する：
- CI チェックがすべて成功（PASS）または実行中（PENDING）
- 未対応のレビューコメントがない
- リンクされた Issue がすべてクローズ済み
CI が実行中（PENDING）の場合も即終了 — 次のループ周回で結果を確認する。
1d. 状況サマリー（対話モードのみ）
対話モードでは状況サマリーを表示し、対応方針の確認を取る。
ステップ 2: CI エラーの解消
CI エラーを分類し、優先度順に対応する。
| 優先度 | エラー種別 | 再現コマンド |
|---|---|---|
| 1 | コンパイルエラー | エラーメッセージから直接特定 |
| 2 | lint / fmt | ./scripts/ci-check.sh ai lint, ./scripts/ci-check.sh ai dylint |
| 3 | テスト失敗 | ./scripts/ci-check.sh ai unit-test, ./scripts/ci-check.sh ai integration-test |
| 4 | clippy | ./scripts/ci-check.sh ai clippy |
| 5 | doc テスト | ./scripts/ci-check.sh ai doc |
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.
- 7d ago First seen · 151 lines · 271 tokens per session scan A 6b37a16c9109
pr-green is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 271 tokens to every session and 1,815 once invoked, about $0.0014 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-09-03.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.