Gentleman Guardian Angel is an AI code-review tool that checks staged files against a repository’s coding standards. Developers use it as a Git pre-commit hook or to review full pull requests, with different AI providers available. The catalogue add-ons support its workflows.
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 skills add Gentleman-Programming/gentleman-guardian-angel --skill branch-prgit clone --depth 1 https://github.com/Gentleman-Programming/gentleman-guardian-angelWrote 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/skills/gentleman-programming/gentleman-guardian-angel/branch-pr)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-guardian-angel/branch-pr"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/branch-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-guardian-angel/branch-pr"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/branch-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00768 |
| Opus 5 | $0.00000 | $0.00384 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
branch-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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: gga-branch-pr
Purpose
Standardize branch creation and PR submission for the GGA project.
When to Use
When creating a pull request, opening a PR, or preparing changes for review.
Branch Naming
Format: type/description — validated by regex:
^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)\/[a-z0-9._-]+$
| Type | Example |
|---|---|
| feat | feat/ollama-streaming |
| fix | fix/hook-marker-injection |
| docs | docs/contributing-labels |
| chore | chore/update-shellspec |
| refactor | refactor/cache-lookup |
| test | test/integration-ci-mode |
| ci | ci/split-test-jobs |
| style | style/output-formatting |
| perf | perf/cache-lookup-speed |
| build | build/makefile-targets |
| revert | revert/broken-hook-change |
Rules: description must be lowercase, only a-z, 0-9, ., _, -.
PR Workflow
- Create branch from main:
git checkout -b type/description main - Make changes following relevant skills (shellcheck-standards, testing-coverage)
- Run validation:
make lint && make test - Push branch:
git push -u origin type/description - Create PR:
gh pr create --title "type(scope): description" --body "..."
PR Title Format
Must match conventional commits regex:
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z0-9\._-]+\))?!?: .+
Valid scopes: providers, hooks, cache, cli, ci, config, install
Examples:
feat(providers): add GitHub Models provider supportfix: crash on startupfix!: change hook marker format
PR Body Template
## Summary
<!-- What does this PR do? -->
## Changes
-
## Testing
- [ ] `make lint` passes
- [ ] `make test` passes
Closes #N
Critical Rules
- Every PR MUST link an approved issue:
Closes #Nin the body - Every PR MUST have exactly one
type:*label - NEVER include
Co-Authored-Bytrailers of any kind - Run
make lint && make testbefore pushing — no exceptions - PRs against unapproved issues will be closed without review
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.
- 12d ago First seen · 85 lines · 0 tokens per session scan A 656a54a0b441
branch-pr is a skill published in the GitHub repository Gentleman-Programming/gentleman-guardian-angel (1,149 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 768 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-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.