Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kyleoliveiro/sg-gov-skills --skill singpass-legacygit clone --depth 1 https://github.com/kyleoliveiro/sg-gov-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/singpass-legacy)<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/singpass-legacy"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/singpass-legacy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/singpass-legacy"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/singpass-legacy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00210 | $0.02820 |
| Opus 5 | $0.00105 | $0.01410 |
| Sonnet 5 | $0.00042 | $0.00564 |
| Haiku 4.5 | $0.00021 | $0.00282 |
Grade A, and why
singpass-legacy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Singpass legacy: Myinfo v3/v4 and the pre-FAPI authentication API
Three distinct legacy surfaces are still running in production across agencies. Identify which one you are looking at before touching 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 — decryption code is not portable, and
neither are client assertions (aud differs per system).
Deadlines:
- Myinfo v3/v4 → v5: end Sep 2026 (per the current Myinfo FAQ; the legacy v4 FAQ still shows a stale "30 Sept 2025" — the live current-docs date governs). v3/v4 onboarding is discontinued and the official connectors are frozen.
- All Singpass apps FAPI 2.0-compliant by 31 Dec 2026 (banner on every pre-FAPI docs page).
- The last Myinfo v3 X.509 verification certificate expired 7 Nov 2024 — still-running v3 services must have downloaded the renewed cert and toggled "Renewed certificate" in the SDP app details, or signature verification breaks.
For anything new, use the singpass skill. This skill's jobs: keep legacy integrations alive until migration, and execute the migration without the silent breakages.
Source and currency
Embedded from the legacy sections of https://docs.developer.singpass.gov.sg as of
2026-07-23 (append .md to page URLs for markdown). Full wire formats, error
tables, and migration checklists: references/legacy-surfaces-and-migration.md.
Caution: the "Technical Concepts" pages filed under the pre-FAPI docs tree are
actually FAPI-era content (they reference PAR/DPoP and the /fapi audience) —
don't treat them as pre-FAPI-normative.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 166 lines · 210 tokens per session scan A fdfc0da7df4b
singpass-legacy is a skill published in the GitHub repository kyleoliveiro/sg-gov-skills (16 stars, last pushed 1mo ago), licensed MIT. It adds 210 tokens to every session and 2,820 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…