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/kickflow/kickflow-mcp-server/create-prgit clone --depth 1 https://github.com/kickflow/kickflow-mcp-serverWhat 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.00000 | $0.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
create-pr 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 2d 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.
What it actually says
現在のブランチをGitHubにプッシュし、プルリクエストを作成します。 ユーザーに質問がある場合は、1つずつ必ず尋ねてください。 以下の手順を必ず遵守してください。勝手に手順を飛ばしたりコミットすることは禁止です。
手順
-
現在のブランチを確認し、GitHubにプッシュします。
git branch --show-currentで現在の[ブランチ名]を確認します。git push origin [ブランチ名]を実行します。
-
Pull Requestの[マージ先ブランチ]をユーザーに尋ねてください。その際、以下のコマンドでRemoteのbranchをすべて表示して「どのブランチにマージしますか？」と質問してください。
git fetch origin && git branch --remotes | grep origin | grep -v -- '->' | grep -v 'renovate/' | sed 's| *origin/||'
-
現在のブランチで発生した差分を以下のコマンドで確認して、実装内容を把握して[やったこと]として簡潔に要約してください。
git diff origin/[マージ先ブランチ]...[ブランチ名]
-
次に[PRの説明]を[プロジェクトフォルダ]/.github/pull_request_template.mdのテンプレートに従って作成します。
- テンプレートにあるコメントに従って、必要な情報を記入してください。
- テンプレート内の[やったこと]は、3.で確認した内容をコメントの指示に従って記入してください
-
Pull Requestを作成します。
gh pr create --base [マージ先ブランチ] --title "[PRのタイトル]" --body "[PRの説明]"を実行します。- [PRのタイトル]は、実装内容を簡潔に表現した日本語のタイトルを作成してください。
- [PRの説明]は、4.で作成した内容をそのまま貼り付けてください。
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.
- 2d ago First seen · 25 lines · 0 tokens per session scan A ecf03f8a435e
create-pr is a command published in the GitHub repository kickflow/kickflow-mcp-server (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 494 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.