verify-governance SKILL.md skillB
verify-governance from nxtg-ai/forge-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nxtg-ai/forge-plugin/verify-governance@git:20261007.1acb8b5Pins git:20261007.1acb8b5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nxtg-ai/forge-plugin
- Path
plugins/nxtg-forge/skills/verify-governance/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.1acb8b5, committed Oct 7, 2026
- First version recorded
- Feb 7, 2026
- Size
- 10,063 bytes
- Repository stars
- 6
- License
- MIT
Adjudicate a flagged governance concern with evidence, then issue a JUSTIFIED or REVERT verdict. Use when a Forge governance hook logs "GOVERNANCE: N violation(s)" or "Code governance", when a test-vs-implementation mismatch is suspected, when a change might be out of directive scope, or when the user asks to verify/justify a code or test change. Reads the real implementation before ruling — it never guesses.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verify Governance Skill Adjudicates a governance concern by reading the **actual** source, comparing it to what was flagged, and returning an evidence-backed verdict: **JUSTIFIED** (proceed) or **REVERT**. This is the manual/adjudication front end for the same concern class the `governance-verifier` agent handles automatically. Use this skill for a quick in-session ruling; delegate to the agent when the concern needs its own isolated context. ## When to Use - A Forge advisory hook printed a warning during an Edit/Write (`GOVERNANCE: N violation(s)`). - You changed a test assertion and need to prove it matches the implementation. - You suspect a change drifted outside the current directive scope. - The user asks "is this justified?" / "should I revert this?". ## What the hooks actually emit (ground truth) `hooks/scripts/governance-check.sh` is a **PostToolUse (Edit/Write) advisory** hook — it **always exits 0 and never blocks**. It only runs on source paths (`*/src/*`, `.ts/.tsx/.js/.jsx/.py/.rs/.go`), **skips test files** (`*.test.*`, `*.spec.*`, `*__tests__*`), and flags four categories: | Tag | Rule | Message fragment | |-----|------|------------------| …
Read the whole file at its exact version.
How to install
mdr add nxtg-ai/forge-plugin/verify-governance@sha256:78366e66ca81dbf1The line at the top of this page pins the label git:20261007.1acb8b5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_76ueidc33lvtcjyb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 7, 2026 and Oct 7, 2026, about one every 60 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.1acb8b5 latest | 2026-10-07 | 1acb8b5 | 10,063 B | B | view · diff |
| git:20260714.4fd0952 | 2026-07-14 | 4fd0952 | 8,916 B | A | view · diff |
| git:20260714.061716b | 2026-07-14 | 061716b | 4,588 B | A | view · diff |
| git:20260308.688ea23 | 2026-03-08 | 688ea23 | 4,564 B | A | view · diff |
| git:20260207.88c1f6e | 2026-02-07 | 88c1f6e | 4,576 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:5051)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10063 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
nxtg-ai/forge-plugin · 6 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_76ueidc33lvtcjyb GET https://markdownregistry.com/api/v1/resolve?ref=nxtg-ai/forge-plugin/verify-governance GET https://markdownregistry.com/api/v1/blob/78366e66ca81dbf103d48b61c7062e5caf5542d47acf736759ff8ba728d258dd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.