crypto-validation SKILL.md skillA
crypto-validation from ethanolivertroy/grclanker is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ethanolivertroy/grclanker/crypto-validation@git:20260406.08026f1Pins git:20260406.08026f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ethanolivertroy/grclanker
- Path
cli/.pi/skills/crypto-validation/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260406.08026f1, committed Apr 6, 2026
- Size
- 1,796 bytes
- Repository stars
- 23
- License
- Apache-2.0
Validate cryptographic module FIPS compliance and check for known vulnerabilities. Use when assessing whether an organization's cryptographic implementations meet federal validation requirements (FIPS 140-2/140-3, NIST SC-13, FedRAMP cryptographic module guidance).
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
# Cryptographic Module Validation ## When to Use - User asks about FIPS validation status of a crypto module or vendor - User needs to verify cryptographic compliance for FedRAMP/CMMC/federal systems - User asks about the security of a specific cryptographic library (OpenSSL, BoringSSL, etc.) - User needs to check if crypto modules have known exploited vulnerabilities ## Workflow 1. **Search active modules** — Use `cmvp_search_modules` with vendor/module name 2. **Check historical** — If not found active, use `cmvp_search_historical` for expired/revoked certs 3. **Check pipeline** — Use `cmvp_search_in_process` for modules awaiting validation 4. **Cross-reference vulnerabilities** — Use `kevs_search` with the vendor/product 5. **Score exploit risk** — Use `kevs_get_epss` for any CVEs found 6. **Map to controls** — Reference NIST SP 800-53 SC-13 (Cryptographic Protection) ## Key Controls - **NIST SC-13**: Cryptographic Protection — requires FIPS-validated cryptography - **NIST SC-12**: Cryptographic Key Establishment and Management - **FedRAMP**: References NIST SP 800-175B for crypto module requirements - **CMMC**: SC.L2-3.13.11 — Employ FIPS-validated cryptography …
Read the whole file at its exact version.
How to install
mdr add ethanolivertroy/grclanker/crypto-validation@sha256:25230810db0f82c3The line at the top of this page pins the label git:20260406.08026f1, 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_7vonrz5wwfvxlov3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 6, 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 (1796 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
ethanolivertroy/grclanker · 23 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7vonrz5wwfvxlov3 GET https://markdownregistry.com/api/v1/resolve?ref=ethanolivertroy/grclanker/crypto-validation GET https://markdownregistry.com/api/v1/blob/25230810db0f82c3787ff5e27eab48fda567eb28c164a12f076d8d72de93a3d5
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.
More from ethanolivertroy/grclanker
Every file in ethanolivertroy/grclanker