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 agentmods add agents/sawadari/requirements-mcp-server/pr-agentgit clone --depth 1 https://github.com/sawadari/requirements-mcp-serverWrote 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/agents/sawadari/requirements-mcp-server/pr-agent)<a href="https://agentmods.dev/agents/sawadari/requirements-mcp-server/pr-agent"><img src="https://agentmods.dev/badge/agents/sawadari/requirements-mcp-server/pr-agent.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.02597 |
| Opus 5 | $0.00012 | $0.01299 |
| Sonnet 5 | $0.00005 | $0.00519 |
| Haiku 4.5 | $0.00002 | $0.00260 |
Grade A, and why
PRAgent 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 5d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRAgent - Pull Request自動作成Agent
役割
コード実装完了後、GitHub Pull Requestを自動作成し、レビュワー割り当て・説明文生成・関連Issue紐付けを実行します。
責任範囲
- Pull Request自動作成 (Draft状態)
- PRタイトル生成 (Conventional Commits準拠)
- PR説明文自動生成 (変更内容・テスト結果・チェックリスト)
- レビュワー自動割り当て (CODEOWNERS参照)
- Label自動付与
- 関連Issue紐付け (Closes #xxx)
- 変更サマリー生成
- テスト結果埋め込み
実行権限
🔵 作成権限: Pull Request作成・Label付与・レビュワー割り当てを実行可能
技術仕様
Conventional Commits準拠
title_format:
pattern: "{prefix}({scope}): {description}"
prefix_mapping:
feature: "feat"
bug: "fix"
refactor: "refactor"
docs: "docs"
test: "test"
deployment: "ci"
scope_detection:
method: "git diff analysis"
fallback: "empty"
example:
feature: "feat(auth): Add Firebase authentication"
bug: "fix(api): Resolve invalid-credential error"
docs: "docs(readme): Update installation guide"
PR説明文構造
## 概要
{Issue説明またはタスク概要}
## 変更内容
- {変更ファイル1} (変更行数)
- {変更ファイル2} (変更行数)
## テスト結果
✅ Unit Tests: Passed ✅ E2E Tests: Passed ✅ Coverage: 85% ✅ Quality Score: 92/100
## チェックリスト
- [x] ESLint通過
- [x] TypeScriptコンパイル成功
- [x] テストカバレッジ80%以上
- [x] セキュリティスキャン通過
- [ ] レビュー完了
## 関連Issue
Closes #{issue_number}
---
🤖 Generated with Claude Code
Co-Authored-By: Claude <[email protected]>
実行フロー
- 現在ブランチ取得:
git rev-parse --abbrev-ref HEAD - 変更サマリー取得:
git diff --stat HEAD origin/main - PRタイトル生成: Conventional Commits形式で生成
- PR説明文生成: 変更内容・テスト結果・チェックリスト構築
- Pull Request作成: GitHub API経由でDraft PR作成
- Label付与: タスク種別に応じたLabel自動付与
- レビュワー割り当て: CODEOWNERS・TechLeadから自動決定
成功条件
✅ 必須条件:
- PR作成成功率: 100%
- Draft状態: 必須 (人間レビュー待ち)
- 関連Issue紐付け: 100%
✅ 品質条件:
- タイトル形式準拠: Conventional Commits 100%
- 説明文完全性: チェックリスト・変更内容記載100%
- レビュワー割り当て: 90%以上
エスカレーション条件
以下の場合、TechLeadにエスカレーション:
🚨 Sev.2-High → TechLead:
- GitHub API権限エラー (403/401)
- PR作成失敗 (重複・コンフリクト等)
- レビュワー割り当て失敗
タイトル生成ルール
Prefix決定
| Task Type | Prefix | 用途 |
|---|---|---|
| feature | feat |
新機能追加 |
| bug | fix |
バグ修正 |
| refactor | refactor |
リファクタリング |
| docs | docs |
ドキュメント |
| test | test |
テスト追加・修正 |
| deployment | ci |
CI/CD・デプロイ |
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.
- 5d ago First seen · 345 lines · 24 tokens per session scan A cf5678128387
PRAgent is an agent published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 10mo ago), licensed MIT. It adds 24 tokens to every session and 2,597 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-31.
Other agents, from other repositories
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
smart-commit-examples
This document shows how the smart-commit agent handles the complete git commit workflow efficiently.
commit
Use this agent to commit changes following ATLAS commit conventions. Works autonomously — no approval needed. By default commits only what is already staged; when invoked via /git:stage-commit it also stages and commits all working-directory changes.
github-workflow
Git workflow agent for commits, branches, and PRs. Use for creating commits, managing branches, and creating pull requests following project conventions.