github-inspector-expert SKILL.md skillA
github-inspector-expert from grcengclub/claude-grc-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grcengclub/claude-grc-engineering/github-inspector-expert@git:20260413.a297aa2Pins git:20260413.a297aa2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grcengclub/claude-grc-engineering
- Path
plugins/connectors/github-inspector/skills/github-inspector-expert/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260413.a297aa2, committed Apr 13, 2026
- Size
- 5,310 bytes
- Repository stars
- 430
- License
- a license file GitHub does not identify
Expertise in evaluating GitHub repositories for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret gh CLI output.
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
# github-inspector expert
You are the interpretation layer between raw GitHub configuration data and compliance frameworks. Your job is to:
1. Understand what each github-inspector check evaluates and why it matters for compliance.
2. Interpret failure modes correctly — distinguish "this is genuinely non-compliant" from "we couldn't tell."
3. Explain findings to practitioners in framework-appropriate language.
## Checks this connector runs (v0.1.0)
| SCF ID | Check | API calls | Fail condition | Severity |
|---|---|---|---|---|
| CHG-02 | Default branch protection exists | `/repos/{o}/{r}/branches/{b}/protection` | 404 or no rule | high |
| CHG-02 | Branch protection requires review | same | required_approving_review_count < 1 | medium |
| CHG-02.1 | Required status checks configured | same | no checks list | medium |
| MON-01 | Secret scanning enabled | repo object `security_and_analysis.secret_scanning.status` | `disabled` | high |
| MON-01.4 | Dependabot alerts enabled | `/repos/{o}/{r}/vulnerability-alerts` | 404 | medium |
| IAO-04 | Code scanning enabled | `/repos/{o}/{r}/code-scanning/alerts` | 404 or "not enabled" | medium |
…Read the whole file at its exact version.
How to install
mdr add grcengclub/claude-grc-engineering/github-inspector-expert@sha256:5e8afcab523ba85dThe line at the top of this page pins the label git:20260413.a297aa2, 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_mb5une5izku67skp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 13, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5310 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 link to a raw IP address
- pass: No script tag
Source
grcengclub/claude-grc-engineering · 430 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mb5une5izku67skp GET https://markdownregistry.com/api/v1/resolve?ref=grcengclub/claude-grc-engineering/github-inspector-expert GET https://markdownregistry.com/api/v1/blob/5e8afcab523ba85d45781538377b7b0ccb74b04106a489e4de8a71f44a9f14a0
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.