Agent skill · writing content · borghei
prompt-governance
This skill should be used when the user asks to "audit prompts for safety", "check prompts for injection vulnerabilities", "manage a prompt catalog", "version control prompts", or "review prompt quality and compliance".
Why this skill is useful
Adds executable scripts for auditing and managing prompts that ensure safety and compliance, which the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 2k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Prompt Governance Category: Engineering Domain: AI Governance Overview The Prompt Governance skill provides tools for auditing prompts for security vulnerabilities, bias, and safety issues, plus managing a versioned catalog of approved prompts. Essential for organizations deploying LLM-based applications at scale. Clarify First Before auditing or cataloging, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Target prompt(s) — the exact file/text to audit or the catalog dir to manage (the subject of every check) [ ] Task: audit vs catalog management — selects promptauditor.py vs promptcatalogmanager.py and the whole workflow [ ] Check focus — injection / bias / safety (sets which auditor checks run and the pass/fail bar) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Quick Start Tools Overview Tool Purpose Key Flags ------ --------- ----------- promptauditor.py Audit prompts for injection, bias, and safety --file, --text, --checks, --format promptcatalogmanager.py Manage versioned prompt catalog --init, --add, --list, --diff, --catalog-dir Workflows Prompt Review Process 1. Author writes or modifies a prompt 2. Run promptauditor.py for automated checks 3. Review findings and address critical issues 4. Add approved prompt to catalog with promptcatalogmanager.py 5. Deploy from catalog (never from ad-hoc sources) Prompt Versioning 1. Store all prompts in catalog with semantic versioning 2. Use --diff to compare versions before promotion 3. Maintain audit trail of all prompt changes 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/prompt-governance