Home / kyleoliveiro / sg-gov-skills · GitHub

sg-gov-singpass-legacy SKILL.md skillA

sg-gov-singpass-legacy from kyleoliveiro/sg-gov-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kyleoliveiro/sg-gov-skills/sg-gov-singpass-legacy@git:20261027.6f21efa

Pins git:20261027.6f21efa in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kyleoliveiro/sg-gov-skills
Path: skills/sg-gov-singpass-legacy/SKILL.md
Versions recorded: 1
Latest version: git:20261027.6f21efa, committed Oct 27, 2026
Size: 9,962 bytes
Repository stars: 17
License: MIT

Maintain, debug, or migrate a LEGACY Singpass integration — Myinfo v3 (client_secret + PKI_SIGN X.509 signing, /com/v3/authorise), Myinfo v4 (OAuth 2.1 client assertions + DPoP, /com/v4), or the pre-FAPI 2.0 Singpass authentication API (direct /auth redirect, comma-separated sub like "s=S1234567A,u=uuid"). Use this whenever an existing Singpass or Myinfo integration predates Feb 2026, when code references PKI_SIGN, client_secret, api.myinfo.gov.sg, attributes=, purpose_id, person/{sub}, or…

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

# Singpass legacy: Myinfo v3/v4 and the pre-FAPI authentication API

Three legacy surfaces are still in production across agencies. Identify which
one you are working on before changing anything:

| Surface | Endpoints | Client auth | Payload crypto |
|---|---|---|---|
| **Myinfo v3** | `api.myinfo.gov.sg/com/v3/*` (`/authorise` — British spelling) | `client_id` + **`client_secret`** + `Authorization: PKI_SIGN` RS256 base-string signature keyed by an **X.509 RSA cert** | JWE **RSA-OAEP + A256GCM** wrapping RS256 JWS |
| **Myinfo v4** | `api.myinfo.gov.sg/com/v4/*` (`/authorize`) | ES256 client assertion (`aud` = the API URL, adds `cnf.jkt`) + **DPoP**; no secret, no X.509 | JWE **ECDH-ES+A256KW + A256GCM** wrapping ES256 JWS |
| **Pre-FAPI Singpass auth API** | `id.singpass.gov.sg` — `/auth`, `/token`, `/userinfo` (no `/fapi` prefix, no PAR) | `private_key_jwt` (`aud` = bare issuer URL), PKCE S256 | ID token JWS, or JWS-in-JWE (**ECDH-ES+A\*KW + A256CBC-HS512**) for PII clients |

The JWE recipes differ across all three, so decryption code is not portable
between them. Client assertions are not portable either (`aud` differs per
system).

**Deadlines:**
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kyleoliveiro/sg-gov-skills/sg-gov-singpass-legacy@sha256:69826905bf2e200a

The line at the top of this page pins the label git:20261027.6f21efa, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_lr6ztpt6jlvuxhdo.svg)](https://markdownregistry.com/a/art_lr6ztpt6jlvuxhdo)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 27, 2026.

version	committed	commit	size	audit
git:20261027.6f21efa latest	2026-10-27	6f21efa	9,962 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9962 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

GitHub

kyleoliveiro/sg-gov-skills · 17 stars · license MIT · pushed 2026-11-02 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lr6ztpt6jlvuxhdo
GET https://markdownregistry.com/api/v1/resolve?ref=kyleoliveiro/sg-gov-skills/sg-gov-singpass-legacy
GET https://markdownregistry.com/api/v1/blob/69826905bf2e200aac8e65f67078a70cd5f978cc532a2fd36be57ba99e447948

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.