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 commands/sawadari/requirements-mcp-server/create-issuegit 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/commands/sawadari/requirements-mcp-server/create-issue)<a href="https://agentmods.dev/commands/sawadari/requirements-mcp-server/create-issue"><img src="https://agentmods.dev/badge/commands/sawadari/requirements-mcp-server/create-issue.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.00012 | $0.02443 |
| Opus 5 | $0.00006 | $0.01222 |
| Sonnet 5 | $0.00002 | $0.00489 |
| Haiku 4.5 | $0.00001 | $0.00244 |
Grade A, and why
create-issue 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 4d 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue Command
Agent実行用のIssueをテンプレートベースで対話的に作成します。
使用方法
/create-issue
このコマンドを実行すると、対話的にIssue作成のための情報を収集します。
対話フロー
1. Issue タイトル
Issue タイトルを入力してください:
例) ユーザー認証機能の実装
2. Issue タイプ選択
Issue タイプを選択してください:
1. 🆕 feature (新機能)
2. 🐛 bug (バグ修正)
3. ♻️ refactor (リファクタリング)
4. 📝 docs (ドキュメント)
5. ⚡ performance (パフォーマンス改善)
6. 🔒 security (セキュリティ)
7. 🧪 test (テスト追加)
選択 (1-7):
3. 要件入力
要件を入力してください (完了したら空行):
- ログイン画面の実装
- JWT認証の実装
- ユーザーモデルの作成
- ユニットテスト作成
<Enter>
4. 技術スタック (オプション)
使用する技術スタックを入力してください (任意):
例) React, TypeScript, Firebase Auth
5. 制約事項 (オプション)
制約事項があれば入力してください (任意):
例) パスワードリセット機能は別Issueで実装
6. Agent実行設定
Agent自動実行を有効にしますか? (y/n):
y: 🤖agent-execute ラベルを自動付与（作成後すぐにAgentが実行開始）n: 手動でラベルを追加するまでAgent実行しない
7. 優先度設定
優先度を選択してください:
1. 🔴 High (高)
2. 🟡 Medium (中)
3. 🟢 Low (低)
選択 (1-3):
8. 担当者指定 (オプション)
担当者を指定しますか? (GitHubユーザー名、空でスキップ):
生成されるIssue
Issue Body テンプレート
# [タイプ] タイトル
## 📋 要件
- [ ] 要件1
- [ ] 要件2
- [ ] 要件3
## 🛠️ 技術スタック
- React
- TypeScript
- Firebase Auth
## ⚠️ 制約事項
- パスワードリセット機能は別Issueで実装
## 📊 成功条件
- [ ] TypeScript エラー: 0件
- [ ] テストカバレッジ: ≥80%
- [ ] 品質スコア: ≥80点
- [ ] セキュリティスキャン: 脆弱性0件
## 🤖 Agent実行設定
- **自動実行**: 有効
- **優先度**: High
- **期待実行時間**: 3-5分
---
**ラベル**: 🤖agent-execute, 🆕feature, 🔴priority-high
🤖 Generated with [Claude Code](https://claude.com/claude-code)
実行例
Example 1: 新機能Issue作成
/create-issue
🤖 Agent Issue Creator
Issue タイトルを入力してください:
> ユーザープロフィール編集機能
Issue タイプを選択してください:
1. 🆕 feature
...
> 1
要件を入力してください (完了したら空行):
> プロフィール編集画面UI
> プロフィール更新API
> バリデーション実装
> ユニットテスト作成
>
技術スタックを入力してください (任意):
> React, TypeScript, REST API
制約事項があれば入力してください (任意):
> パスワード変更は別機能として実装
Agent自動実行を有効にしますか? (y/n):
> y
優先度を選択してください:
1. 🔴 High
2. 🟡 Medium
3. 🟢 Low
> 2
担当者を指定しますか? (GitHubユーザー名、空でスキップ):
>
✅ Issue作成完了
Issue番号: #123
URL: https://github.com/owner/repo/issues/123
🤖 Agent実行が開始されます (約3-5分)
進捗確認: npm run agents:parallel:exec -- --issue 123 --dry-run
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.
- 4d ago First seen · 404 lines · 12 tokens per session scan A cee07f3db6a0
create-issue is a command published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 2,443 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 commands, from other repositories
project-recap
Generate a visual project recap for context switching.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).