testssl-inspector-expert SKILL.md skillA
testssl-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/testssl-inspector-expert@git:20260628.e201220Pins git:20260628.e201220 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/testssl-inspector/skills/testssl-inspector-expert/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260628.e201220, committed Jun 28, 2026
- First version recorded
- May 14, 2026
- Size
- 7,381 bytes
- Repository stars
- 430
- License
- a license file GitHub does not identify
Interpret testssl-inspector normalized findings, recommend remediations, and tie evidence back to SCF anchor controls plus SOC 2 / NIST 800-53 r5 / PCI DSS 4.0.1 / ISO 27002:2022 equivalents derived from SCF crosswalks.
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
# testssl Inspector Expert Use this skill when reviewing findings produced by `/testssl-inspector:scan`. The connector wraps `testssl.sh` and emits v1 Findings against `tls_endpoint` resources; this skill translates those into remediation advice an engineer can act on and audit evidence a reviewer can sign off. ## Reading the output Findings live at `~/.cache/claude-grc/findings/testssl-inspector/<run_id>.json`. Each document covers one TLS endpoint: - `resource.type = "tls_endpoint"`, `resource.id = "<host>:<port>"`, `resource.uri = "https://<host>:<port>/"` for HTTPS or `resource.uri = "starttls+<proto>://<host>:<port>/"` for STARTTLS scans - `evaluations[]` — one entry per (control_framework, control_id, testssl finding) tuple - `findings[]` — narrative roll-up for CVEs and critical results (cap 50 per doc) - `metadata.target`, `metadata.effective_target`, `metadata.host`, `metadata.port`, `metadata.starttls` — the original input, the port-expanded target actually scanned, the parsed host/port, and the STARTTLS protocol when applicable ## What testssl IDs mean Most fails fall into one of five families. The remediation pattern is the same within each family. …
Read the whole file at its exact version.
How to install
mdr add grcengclub/claude-grc-engineering/testssl-inspector-expert@sha256:bff66fcdabfd529dThe line at the top of this page pins the label git:20260628.e201220, 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_qlwdwkotyvbbstxf)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 14, 2026 and Jun 28, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260628.e201220 latest | 2026-06-28 | e201220 | 7,381 B | A | view · diff |
| git:20260626.4ee5221 | 2026-06-26 | 4ee5221 | 7,282 B | A | view · diff |
| git:20260515.9766c1b | 2026-05-15 | 9766c1b | 7,138 B | A | view · diff |
| git:20260514.f780b52 | 2026-05-14 | f780b52 | 6,107 B | A | view |
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 (7381 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_qlwdwkotyvbbstxf GET https://markdownregistry.com/api/v1/resolve?ref=grcengclub/claude-grc-engineering/testssl-inspector-expert GET https://markdownregistry.com/api/v1/blob/bff66fcdabfd529d9786df86c8b1e0a0641885bf60055e587af02133a6522a46
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.