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/nimble-giant/ailloy/open-prgit clone --depth 1 https://github.com/nimble-giant/ailloyWrote 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/nimble-giant/ailloy/open-pr)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/open-pr"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/open-pr.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.00345 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
open-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 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.
What it actually says
open-pr
Open a pull request for the current branch with automatically generated description, or update existing PR.
Usage
/open-pr [draft]
Options
draft- Creates the PR in draft mode (optional, defaults to ready for review)
Workflow
When this command is used, Claude will:
-
Enter Plan Mode to outline the PR creation/update process
-
Check for existing PR on the current branch using
gh pr view --json number,title,url,state -
If PR already exists:
- Use
/update-prto update the existing PR description - Skip to step 6
- Use
-
If no PR exists:
- Generate PR description using
/pr-descriptioncommand - Create new PR using
gh pr create
- Generate PR description using
-
Set PR status:
- Default: Ready for review
- With
draftflag: Draft mode
-
Display PR URL for user to review
Examples
/open-pr- Create PR ready for review/open-pr draft- Create PR in draft mode
Integration
This command integrates with:
/pr-description- For generating PR descriptions/update-pr- For updating existing PRs/gh-issue- Includes issue references if branch was created for an issue
Notes
- Automatically detects existing PRs to avoid duplicates
- Uses GitHub CLI (
gh) for all PR operations - Puts Claude into Plan Mode for transparency
- Leverages existing
/pr-descriptionfunctionality - Does not include Claude Code attribution in PR descriptions
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 · 57 lines · 0 tokens per session scan A 5a053b0b7335
open-pr is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 345 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.