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 docs-alignmentgit 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/docs-alignment)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-guardian-angel/docs-alignment"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/docs-alignment/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/docs-alignment"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/docs-alignment.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.00621 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
docs-alignment 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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: gga-docs-alignment
Purpose
Keep documentation in sync with every code and workflow change in GGA.
When to Use
Any code or workflow change that affects user or contributor behavior.
Docs Map
| File | Covers |
|---|---|
README.md |
Installation, usage, CLI flags, providers, examples |
CONTRIBUTING.md |
Dev setup, contribution workflow, labels, testing, PR process |
Change → Doc Rules
| If you change... | Update... |
|---|---|
| A CLI flag (add, remove, rename) | README.md — flags table + examples |
| A provider (add, remove, change behavior) | README.md + CONTRIBUTING.md |
| The contribution workflow | CONTRIBUTING.md |
| The label system | CONTRIBUTING.md |
| Test structure or test commands | CONTRIBUTING.md |
| Install/uninstall behavior | README.md |
The .gga config format |
README.md |
| Hook behavior or marker format | README.md + CONTRIBUTING.md |
CI mode behavior (--ci) |
README.md |
Critical Rules
- NEVER reference CLI flags, commands, or scripts that don't exist in code
- NEVER let a PR that changes behavior ship without updating docs
- Docs must describe the FINAL state, not the journey ("now supports X" is wrong)
- Code examples in docs must be tested and accurate
- PRs that change behavior without updating docs should be rejected in review
Verification Checklist
Before submitting a PR with code changes:
[ ] Does this change affect any CLI flags? → update README.md
[ ] Does this change affect provider behavior? → update README.md + CONTRIBUTING.md
[ ] Does this change affect the contribution
workflow or labels? → update CONTRIBUTING.md
[ ] Does this add/remove a config option? → update README.md
[ ] Are all code examples in the docs still
accurate after this change? → verify manually
Anti-patterns
# BAD — README still shows old flag name
README: --cache-dir
Code: --cache-path ← was renamed
# BAD — docs reference non-existent script
README: "run setup.sh to configure" ← setup.sh doesn't exist
# BAD — missing provider in list
README: "Supports: Claude, Gemini, Codex" ← Ollama was just added but not listed
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.
- 9d ago First seen · 72 lines · 0 tokens per session scan A 984e6502f4d4
docs-alignment is a skill published in the GitHub repository Gentleman-Programming/gentleman-guardian-angel (1,145 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 621 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…