functional-safety-signpost SKILL.md skillA
functional-safety-signpost from jgsystemsconsulting/jgs-se-knowledge-packs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/functional-safety-signpost@git:20261012.b19c162Pins git:20261012.b19c162 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jgsystemsconsulting/jgs-se-knowledge-packs
- Path
packs/functional-safety-signpost/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261012.b19c162, committed Oct 12, 2026
- First version recorded
- Sep 27, 2026
- Size
- 3,536 bytes
- Repository stars
- 71
- License
- a license file GitHub does not identify
Signpost (not a knowledge pack) for the functional safety standards landscape: IEC 61508, ISO 26262, ISO/SAE 21434, UL 4600, SAE J3016, and ASPICE. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate a functional safety standard. All six are paywalled or carry no redistribution grant and cannot be packaged; open paths point at US Government packs, which are not equivalents.
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
<!-- argument-hint: [standard designation or topic, e.g. IEC 61508 / ISO 26262 / 21434 / UL 4600 / J3016 / ASPICE] --> # Functional Safety Standards Landscape: Signpost (pointers only) **This is a signpost, not a knowledge pack.** It carries **no source content**: no reproduced clauses, no synthesised summaries of normative text. IEC 61508, ISO 26262, ISO/SAE 21434, UL 4600, SAE J3016, and ASPICE are Excluded under this repo's `docs/SOURCE-VETTING.md` (paywalled or no redistribution grant), so none of them can be reconstituted into a pack. What this skill does: tell you which functional safety standard you want, who owns it, whether it can be packaged, and where to get the authentic copy. ## When to use You need to identify, cite, or locate a functional safety standard (e.g. "the functional safety standard?" → IEC 61508; "the automotive variant?" → ISO 26262). This routes you to the authoritative source. The genuinely open paths in this catalogue are the `mil-std-882` and `nhtsa-vehicle` packs (US Government practice, not equivalents of any excluded row). **Prerequisites:** none. Plain Markdown. ## How to use …
Read the whole file at its exact version.
How to install
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/functional-safety-signpost@sha256:21834f10b0ff5cdcThe line at the top of this page pins the label git:20261012.b19c162, 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_yllzdszg45cxx524)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 27, 2026 and Oct 12, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.b19c162 latest | 2026-10-12 | b19c162 | 3,536 B | A | view · diff |
| git:20260927.31eb968 | 2026-09-27 | 31eb968 | 3,473 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 (3536 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
jgsystemsconsulting/jgs-se-knowledge-packs · 71 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yllzdszg45cxx524 GET https://markdownregistry.com/api/v1/resolve?ref=jgsystemsconsulting/jgs-se-knowledge-packs/functional-safety-signpost GET https://markdownregistry.com/api/v1/blob/21834f10b0ff5cdcf211ae93b43bdb5fc49c9d863e217ff3f363c7197b4178ae
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.