What is sg-gov-security-testing?

A guide to security testing and vulnerability management for Singapore government systems. It covers vulnerability scans, cloud-configuration checks, public reporting through security.txt, penetration tests, and fixing findings within agreed timeframes.

Use it to set up or audit scanning, cloud security checks, penetration testing, vulnerability disclosure, and remediation tracking.

It turns security testing into a managed process rather than a one-time scan. It also makes clear that testing schedules and fix deadlines must come from the project's approved security plan.

sg-gov-security-testing — 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-security-testing

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-security-testing/github.svg)](https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-gov-security-testing)

Your own site

<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-gov-security-testing"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-gov-security-testing/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-security-testing"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-gov-security-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,880 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.00195	$0.02880
Opus 5.5	$0.00078	$0.01152
Sonnet 5.5	$0.00039	$0.00576
Haiku 4.5	$0.00019	$0.00288

Measured 7d ago against content hash 7d0f0f3cfa5e, 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-security-testing 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-security-testing/SKILL.md · 189 lines

How it starts

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

sg-gov-security-testing: ST controls for SG government systems

You are setting up or auditing a security testing and vulnerability management programme against the ICT&SS Policy Reform Security Testing family (ST-1..ST-5). The family covers the testing lifecycle around a running system: scanning hosts for vulnerabilities, continuously checking cloud configuration, giving the public a way to report what they find, commissioning penetration tests, and remediating what all of those surface within committed timeframes.

This family depends on nine agency-defined parameters: scan type and cadence (ST-1), the disclosure channel type (ST-3), the testing type and frequency (ST-4), and four severity-based remediation SLAs (ST-5). The catalog leaves all of them blank. Get the values from the project's System Security Plan; never invent them. A finding of "scans are too infrequent" is only defensible against the SSP's number.

What this family is not about

ST covers the host, cloud, and programme layer. Three things are often wrongly filed under it:

CI code and dependency scanning is not ST-1. SAST (SD-4), SCA/dependency scanning (SD-5), secret detection (SD-6), and pipeline DAST (SD-9) live in Secure Development (sg-gov-secure-pipeline). ST-1 is host-level vulnerability assessment of the VM, instance, and network layer. A repo with Dependabot and CodeQL has no ST-1 coverage; don't accept "we scan continuously" on that basis. Findings from those CI scanners do feed the ST-5 remediation SLAs, in the same register and on the same clock.
Container image scanning is CS (sg-gov-container-security), not ST-1.
Fixing an individual vulnerability is another family's work: a SQL injection fix is AS-2 (sg-gov-secure-coding-as). ST-5 governs the process: triage, priority, the SLA clock, and who may sign a risk acceptance.

Source and currency

Control text in this skill and references/st-controls.md is embedded from info.standards.tech.gov.sg as of 2026-07-22; the ST family page was last updated 24 March 2026. The standards iterate. For any compliance-critical decision, verify against the live page:

Read the full file on GitHub · 189 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 · 189 lines · 195 tokens per session scan A 7d0f0f3cfa5e

Subscribe to this mod's changes

sg-gov-security-testing is a skill published in the GitHub repository kyleoliveiro/sg-gov-skills (17 stars, last pushed 7d ago), licensed MIT. It adds 195 tokens to every session and 2,880 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.