secure-development-policy-from-pipeline SKILL.md skillA
secure-development-policy-from-pipeline from better-isms/grcskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add better-isms/grcskills/secure-development-policy-from-pipeline@git:20261027.94f7f3ePins git:20261027.94f7f3e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- better-isms/grcskills
- Path
skills/tristan-roth/secure-development-policy-from-pipeline/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.94f7f3e, committed Oct 27, 2026
- First version recorded
- Oct 19, 2026
- Size
- 8,848 bytes
- Repository stars
- 56
- License
- MIT
Use this skill when an engineering team needs a secure development policy, or has one that does not match how code really ships, and asks "write our secure SDLC policy", "secure development policy from our CI", "document our code review and scanning for the audit", "what does our pipeline already enforce", "change management for engineers" or "secure coding policy for SOC 2 or CRA". Reads the repositories and pipeline definitions, inventories what is actually enforced…
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
Use this when the policy is missing, when it was copied from a template, or when auditors will sample changes and the team wants the policy to describe what the pipeline proves. You get three documents in a new folder, `./secure-development-policy-from-pipeline/`: a table of what your build and release pipeline actually enforces today, repository by repository (`enforcement-inventory.md`); a draft secure development policy of three to five pages that only promises what that table shows (`secure-development-policy.md`); and a list of gaps and decisions for the engineering lead (`decisions.md`). This skill drafts for a human to review and sign; this skill never marks a control effective. The engineering lead approves the policy. End `secure-development-policy.md` with `## Not checked`: what this run did not read or could not open, what it assumed and what it did not verify, specific to this run. Then add a blank `## Review record` for the approver: reviewer role and competence basis, items sampled and the source each was traced to, what was changed or rejected, one item the draft did not flag and what checking it showed, decision, date and draft version reviewed. …
Read the whole file at its exact version.
How to install
mdr add better-isms/grcskills/secure-development-policy-from-pipeline@sha256:13e2e1ec584d5373The line at the top of this page pins the label git:20261027.94f7f3e, 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_xwfphdrvz2zptdjk)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 19, 2026 and Oct 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.94f7f3e latest | 2026-10-27 | 94f7f3e | 8,848 B | A | view · diff |
| git:20261019.20937b5 | 2026-10-19 | 20937b5 | 8,264 B | A | view · diff |
| git:20261019.3c6cd53 | 2026-10-19 | 3c6cd53 | 8,120 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 (8848 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
better-isms/grcskills · 56 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xwfphdrvz2zptdjk GET https://markdownregistry.com/api/v1/resolve?ref=better-isms/grcskills/secure-development-policy-from-pipeline GET https://markdownregistry.com/api/v1/blob/13e2e1ec584d5373a962163270a7557142c4273593df258be63cfbb01b1f9568
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.