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 secure-pipelinegit 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/secure-pipeline)<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/secure-pipeline"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/secure-pipeline/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/secure-pipeline"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/secure-pipeline.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.00156 | $0.04034 |
| Opus 5 | $0.00078 | $0.02017 |
| Sonnet 5 | $0.00031 | $0.00807 |
| Haiku 4.5 | $0.00016 | $0.00403 |
Grade A, and why
secure-pipeline 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
secure-pipeline: SD + SC controls for SG government delivery
You are configuring or auditing a repo + pipeline against 19 controls from the ICT&SS Policy Reform Cybersecurity Control Catalog: SD-1..SD-10 (Secure Development) and SC-1..SC-9 (Software Supply Chain). These are the controls a security audit will walk through for the delivery pipeline, and most are pure configuration — cheap to set up on day one, expensive to retrofit under audit pressure.
Source and currency
Control text in this skill and references/sd-sc-controls.md is embedded from
info.standards.tech.gov.sg as of 2026-07-16. The standards iterate actively. For any
compliance-critical decision, verify against the live pages:
- SD: https://info.standards.tech.gov.sg/control-catalog/cybersecurity/sd/
- SC: https://info.standards.tech.gov.sg/control-catalog/cybersecurity/sc/
Machine-readable OSCAL: https://github.com/GovtechSG/tech-standards — useful for tooling, but it lags the site; the site is authoritative.
Reference files
references/sd-sc-controls.md— full text of all 19 controls (statement, recommendations, risk statement, parameters). Read it when you need exact wording, e.g. for an audit response or SSP documentation.references/platform-recipes.md— concrete GitHub and GitLab recipes per control, with plan-gating notes and open-source fallbacks (gitleaks, semgrep, trivy, ZAP, cosign). Read it when actually configuring a platform.
Before you start: find the SSP
Every agency system has a System Security Plan (SSP) that selects which controls apply at which level and sets the parameter values. Three of these 19 controls carry agency-defined parameters — the catalog deliberately sets no values:
| Control | Parameter | What the SSP defines |
|---|---|---|
| SD-4 | sd-4_prm_1 | Where static analysis runs (typically "CI/CD pipeline, per merge request") |
| SD-5 | sd-5_prm_1, sd-5_prm_2 | Dependency scan frequency in days, and where it runs |
| SD-6 | sd-6_prm_1, sd-6_prm_2 | Where secret detection runs, and the remediation SLA in days for true positives |
| SD-9 | sd-9_prm_1 | Where dynamic analysis runs |
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.
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 · 265 lines · 156 tokens per session scan A 03cf66bc0a6c
secure-pipeline is a skill published in the GitHub repository kyleoliveiro/sg-gov-skills (16 stars, last pushed 1mo ago), licensed MIT. It adds 156 tokens to every session and 4,034 once invoked, about $0.0008 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.