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 careerchain-ys/stdd --skill review-pr-with-agentsgit clone --depth 1 https://github.com/careerchain-ys/stddWrote 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/careerchain-ys/stdd/review-pr-with-agents)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/review-pr-with-agents"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/review-pr-with-agents/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/careerchain-ys/stdd/review-pr-with-agents"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/review-pr-with-agents.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.00139 | $0.02194 |
| Opus 5 | $0.00069 | $0.01097 |
| Sonnet 5 | $0.00028 | $0.00439 |
| Haiku 4.5 | $0.00014 | $0.00219 |
Grade A, and why
review-pr-with-agents 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 11d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request マルチエージェントレビュー
作成済みのPRを qa-engineer と code-reviewer の2エージェントに並列でレビューさせ、結果を統合してユーザーに報告する。
位置付け
create-pr: PRを新規作成するreview-pr-with-agents（本スキル）: 既にあるPRを専門エージェントに投げてレビューしてもらうauto-implementの Phase 3/4 と観点は重なるが、本スキルはパイプライン全体ではなく「レビュー適用のみ」に切り出した単発操作
1. PR番号の特定
引数で明示的にPR番号（#1198 / 1198）が指定されていればそれを使う。無ければ現在のブランチに紐づくPRを特定する。
# 現在のブランチに紐づくPR番号を取得
gh pr view --json number,title,headRefName,baseRefName,url
該当PRが存在しない場合はその旨をユーザーに伝えて停止（create-pr を案内）。
2. PR情報の収集
次をまとめて把握する：
gh pr view <PR番号> --json number,title,body,headRefName,baseRefName,url,commits,files
git fetch origin <baseRef>
git log --oneline origin/<baseRef>...HEAD
集める情報：
- PR番号・タイトル・概要（body）
- base ブランチ（
.stdd.config.ymlのproject.primary_branch） - 対象コミット一覧（
origin/<base>...HEAD） - 主要な変更ファイル
3. worktree / devcontainer の確定
レビュー対象の作業が走っている worktree を確定する。
git worktree list
該当ブランチの worktree パスを控え、対応する devcontainer コマンドのテンプレを用意する：
devcontainer exec --workspace-folder <WORKTREE_PATH> --override-config <WORKTREE_PATH>/.devcontainer/devcontainer.override.json bash -c "<COMMAND>"
重要: devcontainer コマンドは必ず devcontainer exec から始める（変数代入を先頭に置かない）。プロジェクトの AGENTS.md / CLAUDE.md / memory「devcontainerコマンドパターン」を参照。
4. 2エージェントを並列起動
qa-engineer と code-reviewer を同一メッセージ内の2つの Agent 呼び出しとして同時に起動する。片方を待ってから次を投げてはいけない（並列で効率化する意図）。片方をバックグラウンドにしたい場合は run_in_background: true を併用してよい。
4.1 qa-engineer へのプロンプト雛形
PR #<番号> (ブランチ `<headRef>`) のQAレビューを実施してください。
## PR概要
<タイトル>
<body のサマリ>
## 対象コミット（origin/<base> からの N コミット）
<git log --oneline の結果を貼り付け>
## 作業場所
- worktree: <WORKTREE_PATH>
- devcontainer コマンドテンプレ:
devcontainer exec --workspace-folder <WORKTREE_PATH> --override-config <WORKTREE_PATH>/.devcontainer/devcontainer.override.json bash -c "cd /workspace/<app> && npm test -- --no-cache 2>&1 | tail -80"
## レビュー観点
1. Spec ⇔ テスト ⇔ 実装 の整合性（REQUIREMENTS.md / TECH_DESIGN.md ↔ *.test.* ↔ 実装ファイル）
2. 影響する app のユニットテスト全体 pass/fail（--no-cache で実行）
3. 論理的なバグ・エッジケース
4. seed/マイグレーション変更時は既存データとの整合
## 報告形式
Critical / Major / Minor で分類し、ファイル:行で指摘。テスト結果サマリ含め <文字数制限> 字以内で。
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.
- 11d ago First seen · 160 lines · 139 tokens per session scan A bfbd3e2e80ef
review-pr-with-agents is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 139 tokens to every session and 2,194 once invoked, about $0.0007 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.