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 sg-service-shellgit 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/sg-service-shell)<a href="https://agentmods.dev/skills/kyleoliveiro/sg-gov-skills/sg-service-shell"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-service-shell/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/sg-service-shell"><img src="https://agentmods.dev/badge/skills/kyleoliveiro/sg-gov-skills/sg-service-shell.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.00169 | $0.03360 |
| Opus 5 | $0.00084 | $0.01680 |
| Sonnet 5 | $0.00034 | $0.00672 |
| Haiku 4.5 | $0.00017 | $0.00336 |
Grade A, and why
sg-service-shell 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SG government service shell (DSS: TL + BD + PR)
Every public-facing digital service delivered for a Singapore government agency must implement a common "shell" before any feature work matters: proof of legitimacy (users must be able to tell it is really the government), baseline design practices, and performance/reliability basics. These are codified as 22 controls in three families of the Digital Service Standards (DSS) under the ICT&SS Policy Reform (successor to IM8): TL (Trust & Legitimacy, 6), BD (Baseline Design Practices, 9), PR (Performance & Reliability, 7).
Three of these are Level 0 — mandatory, no deviation permitted — in both DSS profiles. Do those first. Most of the rest are Level 1 (default; skipping one requires documented agency IDSC/CIO/CISO approval in a custom System Security Plan). BD-3/4/5 are Level 2 (best practice).
Source and currency
Control text in this skill and in references/tl-bd-pr-controls.md is embedded from
info.standards.tech.gov.sg as of 2026-07-16. The standards iterate actively — for
compliance-critical decisions, verify against the live catalog:
- https://info.standards.tech.gov.sg/control-catalog/dss/tl/
- https://info.standards.tech.gov.sg/control-catalog/dss/bd/
- https://info.standards.tech.gov.sg/control-catalog/dss/pr/
- SGDS component docs: https://designsystem.tech.gov.sg
- WOGAA onboarding: https://www.wogaa.sg
Read references/tl-bd-pr-controls.md for the full control statements, recommendations,
risk statements, and parameters when you need exact wording.
Build checklist, in priority order
1. Level 0 — mandatory, no deviation
TL-3 — Official Government Banner. Display the Official Government Banner ("A Singapore Government Agency Website") on every page of web-based .gov.sg services, as the topmost component — above the agency logo, above navigation, above everything. Why: it is the single strongest signal users have to distinguish real government services from phishing clones. The control prescribes the SGDS component; in SGDS it is named Masthead:
What ships with it
6 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 · 250 lines · 169 tokens per session scan A 61f21462bfd3
sg-service-shell is a skill published in the GitHub repository kyleoliveiro/sg-gov-skills (16 stars, last pushed 1mo ago), licensed MIT. It adds 169 tokens to every session and 3,360 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…