What is sg-gov-access-control?

An access-control guide for Singapore government systems based on ICT&SS Policy Reform controls. Access control means deciding which people and systems may use which resources, with protections such as MFA and least privilege.

Use it to design or audit account inventories, permissions, MFA, government single sign-on, inactive-account handling, and remote administration access.

It provides a structured way to find excessive permissions, unmanaged accounts, weak administrator login, and unsuitable authentication choices.

sg-gov-access-control — Skill for Claude Code by kyleoliveiro

Install

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.

Any agent

npx skills add kyleoliveiro/sg-gov-skills --skill sg-gov-access-control

Clone the repo

git clone --depth 1 https://github.com/kyleoliveiro/sg-gov-skills

Made for: Claude Code.

Or install cybersecurity, the plugin that ships this one along with the rest of its 10 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control/github.svg)](https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control)

Your own site

<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-gov-access-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 207 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00207	$0.03474
Opus 5.5	$0.00083	$0.01390
Sonnet 5.5	$0.00041	$0.00695
Haiku 4.5	$0.00021	$0.00347

Measured 7d ago against content hash b37614a31e47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sg-gov-access-control 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 7d 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.

skills/sg-gov-access-control/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sg-gov-access-control: AC controls for SG government systems

You are setting up or auditing who and what can access a system, with which credentials, from which devices, and for how long, against the ICT&SS Policy Reform Access Control family (AC-1..AC-16). The family governs accounts, identity, authentication, and privilege from creation to removal.

Three points apply throughout:

Medium-Risk Cloud puts AC-2, AC-3, AC-5, AC-6 at Level 0: MFA for privileged accounts, disabling inactive/expired accounts, hardened endpoints for remote admin access, and changing default credentials are mandatory with no deviation path once a system handles Confidential / Sensitive High data. High-Risk Cloud CII adds AC-1 (least privilege) to Level 0.
Identity is split by audience. Public users needing high identity assurance use Singpass/Corppass MFA (AC-7); agency and internal users use Government-managed SSO such as WOG AAD (AC-7's recommendation, enforced through AC-12 SSO with MFA at the IdP). Building a bespoke login for either audience is a finding.
Least privilege is grounded in the inventory. AC-1's statement grants minimum permissions "based on the account inventory implemented". Without the AC-14 inventory of accounts and access rights, deny-by-default has nothing authoritative to check grants against, so build the inventory first.

What this family is not about

Application-layer auth mechanics are AS (sg-gov-secure-coding-as): password policy (AS-5), salted hashing (AS-6), per-request authorisation checks in code (AS-7), secrets storage (AS-8), login rate limiting (AS-4), session timeouts (AS-11). AC owns account and identity governance: a weak password hash is an AS-6 finding; an account nobody disabled is AC-3.
Logging account and access changes is LM (sg-gov-logging-monitoring): LM-4/LM-7 capture account, access-rights, and authentication events; UEBA over account behaviour is LM-20. AC-16's compensating "audit logging and alerting" runs on LM machinery.
Network position is NS. Firewalls, segmentation, and subnet ACLs are Network Security; AC-10 is about not trusting network position: identity and device posture replace VPN reachability.
Singpass/Corppass integration is its own skill. The login plumbing and TX-6 Myinfo pre-fill live in sg-gov-singpass / sg-gov-corppass; sg-gov-service-shell only owns the surrounding DSS page shell (where the button sits). AC-7 is the cybersecurity-side mandate to use Singpass/Corppass MFA at all.
Pipeline hardening is SD/SC (sg-gov-secure-pipeline). CI deploy keys fall under AC-13 rotation, but protected branches and CI gates are Secure Development.

Read the full file on GitHub · 226 lines

Files

What ships with it

7 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.

Changes

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.

7d ago First seen · 226 lines · 207 tokens per session scan A b37614a31e47

Subscribe to this mod's changes

sg-gov-access-control is a skill published in the GitHub repository kyleoliveiro/sg-gov-skills (17 stars, last pushed 7d ago), licensed MIT. It adds 207 tokens to every session and 3,474 once invoked, about $0.0008 per session on Opus 5.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-11-03.