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/insight-services-apac/ingenious/pr-creategit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/pr-create)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/pr-create"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/pr-create.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.1 | $0.00000 | $0.00492 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
pr-create 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Creation
Arguments
$ARGUMENTS- Base branch for the PR (default:to-stable)
Instructions
Use GitHub CLI to create a pull request targeting the base branch specified in $ARGUMENTS. If no argument is provided, use to-stable as the default base branch.
Pre-PR Analysis
Before creating the PR, perform comprehensive change analysis:
- Review all commits: Run
git log origin/main..HEAD --onelineto see all commits in the PR - Review all file changes: Run
git diff origin/main..HEAD --statto see changed files - Review detailed changes: Run
git diff origin/main..HEADto see all code changes - Categorize changes: Group changes by type (features, bug fixes, refactoring, docs, tests, config)
- Identify impact: Note which components/modules are affected
PR Guidelines
CRITICAL Requirements:
- NEVER include emojis in PR titles or descriptions
- Maintain a concise, professional tone in all PR content
- DO NOT add attribution footers (e.g., no "Generated with Claude Code")
- DO NOT use squash merge - preserve all commits
- Use clear, descriptive PR titles in imperative mood
- Account for ALL changes - every modified file must be explained in PR description
- Structure PR description with clear sections:
- Summary: Brief overview of changes
- Changes: Detailed list of modifications by category
- Files Modified: List all changed files with brief description
- Impact: Note any breaking changes or migration steps
Command Format
gh pr create --base <base-branch> --title "Your PR title" --body "Your PR description"
Where <base-branch> is the value from $ARGUMENTS or to-stable if not specified.
Examples
# Using default base branch (to-stable)
gh pr create --base to-stable --title "Add authentication middleware" --body "Add JWT authentication middleware for API endpoints."
# Using custom base branch (e.g., main)
gh pr create --base main --title "Add authentication middleware" --body "Add JWT authentication middleware for API endpoints."
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.
- yesterday First seen · 53 lines · 0 tokens per session scan A 4669716da627
pr-create is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 492 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-09-04.
Other commands, from other repositories
akb-production-review
Review AKB production-governance docs and hooks.
b00t
Show b00t hive status — git, zellij, governance gates, cake balance, open issues.
requirement-review
需求文档多角色评审（requirement-review）：需求文档 → 7-Agent 并行评审 → 重构高质量需求文档（Runtime 受控流程，0-7 阶段状态机）.
wish-review
description: Execute an end-to-end review loop for a wish, combining test execution, Death Testament aggregation, and scoring.
review
Review a change against the repository's rule-driven modern C++ contract.
add-charts
Integrate Chart.js or Recharts for data visualization. Create reusable chart components: line, bar, pie, area, scatter. Implement responsive sizing with container-based dimensions. Add interactive tooltips showing detailed data on hover. Create customizable legends with click-to-hide series. Support real-time data…