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 issue-creationgit 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/issue-creation)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-guardian-angel/issue-creation"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/issue-creation/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/issue-creation"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/issue-creation.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.00493 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
issue-creation 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: gga-issue-creation
Purpose
Standardize issue creation following the issue-first workflow for GGA.
When to Use
When creating a GitHub issue, reporting a bug, or requesting a feature.
Workflow
- Identify issue type: bug or feature
- Use
gh issue createwith the correct template - Fill all required fields completely
- Wait for
status:approvedlabel before opening any PR
Templates
GGA has two templates — NEVER create blank issues (they are disabled):
| Template | Command | Use When |
|---|---|---|
| Bug report | gh issue create --template bug_report.yml |
Something is broken |
| Feature request | gh issue create --template feature_request.yml |
Something is missing |
Bug Report Requirements
Must include:
- GGA version:
gga version - Shell (bash version:
bash --version) - OS (macOS/Linux/distro)
- Provider being used (claude, gemini, codex, ollama)
- Exact reproduction steps
- Expected vs actual behavior
Feature Request Requirements
Must include:
- Problem description (what can't you do today?)
- Proposed solution
- Affected area:
bin/gga,lib/providers.sh,lib/cache.sh, hooks, CI mode, config
Issue Lifecycle
Created → status:needs-review → status:approved → (open PR)
→ status:rejected → (closed, no PR)
Never open a PR for an issue without status:approved.
Critical Rules
- ALWAYS use
gh issue createwith a template - NEVER create blank issues — they are intentionally disabled
- Bug reports MUST include GGA version and provider
- Feature requests MUST describe the problem before the solution
- Issues receive
status:needs-reviewautomatically on creation - Wait for maintainer to add
status:approvedbefore creating a PR
Cookbook
| If... | Then... | Example |
|---|---|---|
| Reporting a bug | Use bug report template, include version + provider | Hook marker injection fails on zsh |
| Requesting a feature | Use feature request template, describe problem first | Can't use gga in Docker without TTY |
| Unsure which template | Default to feature request | Improvement to existing behavior |
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.
- 11d ago First seen · 63 lines · 0 tokens per session scan A dcc150aea6e9
issue-creation 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 493 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.