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/update-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/update-pr)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/update-pr"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/update-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 | $0.00000 | $0.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
update-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
update-pr
Update the description of an existing pull request for the current branch.
Usage
/update-pr
Workflow
When this command is used, Claude will:
-
Enter Plan Mode to outline the PR update process
-
Verify PR exists for the current branch using
gh pr view --json number,title,url,state -
Generate updated description using
/pr-descriptioncommand- Analyzes current branch changes against main
- Creates comprehensive PR description
- Includes issue references if
/gh-issuewas used
-
Update PR description using
gh pr edit --body-file <description-file> -
Confirm update and display PR URL
Integration
This command integrates with:
/pr-description- For generating updated PR descriptions/gh-issue- Includes issue references in the description/open-pr- Called automatically when PR already exists
Error Handling
- If no PR exists for current branch, suggests using
/open-prinstead - If unable to update PR, provides GitHub CLI troubleshooting steps
Notes
- Assumes PR already exists for the current branch
- Regenerates entire description from scratch for accuracy
- Puts Claude into Plan Mode for transparency
- Uses same description format as
/pr-descriptioncommand - Does not include Claude Code attribution in updated 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 · 48 lines · 0 tokens per session scan A 7beb0d008a7f
update-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 295 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.