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/byx-darwin/gitflow-cli/pr-cleanupgit clone --depth 1 https://github.com/byx-darwin/gitflow-cliWhat 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.00892 |
| Opus 5 | $0.00000 | $0.00446 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
pr-cleanup 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gf pr cleanup
Safely clean up branches and worktrees after PR merge.
Synopsis
gf pr cleanup <NUMBER>... [OPTIONS]
gf pr cleanup --merged [OPTIONS]
gf pr cleanup --closed [OPTIONS]
Description
The cleanup command safely removes branches and worktrees associated with merged or closed pull requests. It performs safety checks to prevent accidental deletion of protected branches or the current branch.
This command is particularly useful in worktree-based workflows where gh pr merge --delete-branch fails because the branch is checked out in a worktree.
Arguments
<NUMBER>...
: One or more PR numbers to clean up. Mutually exclusive with --merged and --closed.
Options
--worktree <PATH>
: Remove the specified worktree path after cleanup.
--remote
: Delete remote branches (default: true).
--local
: Delete local branches (default: true).
--force
: Force cleanup of unmerged branches. Bypasses PR state check but not protected branch check.
--dry-run
: Show what would be done without actually deleting anything.
--yes, -y
: Skip interactive confirmation.
--merged
: Clean up all merged PRs. Mutually exclusive with <NUMBER>....
--closed
: Clean up all closed PRs. Mutually exclusive with <NUMBER>....
Safety Checks
The command performs the following safety checks before deletion:
- PR State: Only allows cleanup of merged or closed PRs (unless
--forceis used) - Protected Branches: Refuses to delete protected branches (main, master, develop, release/*)
- Current Branch: Refuses to delete the currently checked-out branch
These checks cannot be bypassed except for the PR state check (using --force).
Worktree Handling
When running in a worktree:
- Automatically detects if currently in a worktree
- Exits the worktree and returns to the main repository
- If
--worktree <PATH>is specified, removes the worktree directory - If
--worktreeis not specified, preserves the worktree directory and displays a message
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 · 151 lines · 0 tokens per session scan A a29c3d410141
pr-cleanup is a command published in the GitHub repository byx-darwin/gitflow-cli (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 892 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.