sg-gov-skills: Instructions file for Codex

AGENTS.md

sg-gov-skills AGENTS.md is an instructions file for Codex, OpenCode from kyleoliveiro/sg-gov-skills. It costs 515 tokens per session, scanned A, original, MIT.

Repository instructions for building software for Singapore government agencies. They describe the project layout and point to topics such as government security, digital identity, accessibility, privacy, security testing, and procurement.

In plain words
What is it for?
Use them when creating or maintaining skills and other project files for Singapore government software.
Why use it?
They give an coding agent the local rules and context needed to work consistently in a government-focused repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions .claude-plugin.

This is kyleoliveiro/sg-gov-skills's own configuration. It tells Codex and OpenCode how to work on sg-gov-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sg-gov-skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kyleoliveiro/sg-gov-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kyleoliveiro/sg-gov-skills/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/kyleoliveiro/sg-gov-skills

Made for: Codex, OpenCode.

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.

agentmods badge for sg-gov-skills AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/kyleoliveiro/sg-gov-skills/agents-md/github.svg)](https://agentmods.dev/instructions/kyleoliveiro/sg-gov-skills/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/kyleoliveiro/sg-gov-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/kyleoliveiro/sg-gov-skills/agents-md/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.

agentmods 80×15 button for sg-gov-skills AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/kyleoliveiro/sg-gov-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/kyleoliveiro/sg-gov-skills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 515 This file is loaded in full into every session.
When invoked 515 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00515 $0.00515
Opus 5.5 $0.00206 $0.00206
Sonnet 5.5 $0.00103 $0.00103
Haiku 4.5 $0.00052 $0.00052

Measured yesterday against content hash db7b805429ea, 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-skills AGENTS.md 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 yesterday.

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.

AGENTS.md · 20 lines

How it starts

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

Agent skills for developers building tech projects for Singapore government agencies.

The skills cover the requirements specific to government delivery: the ICT&SS Policy Reform (IM8's successor) and its System Security Plans, the Cybersecurity and Digital Service Standards control catalogs, Singpass, Corppass, and Myinfo integration, SGDS, and WCAG 2.2 accessibility. Each skill is small, covers one concern, and must work with any agent and model.

Repository layout

  • skills/<skill-name>/SKILL.md: the published skills. This is the layout the skills CLI discovers, so consumers install with npx skills add kyleoliveiro/sg-gov-skills. Authoring conventions live in skills/README.md.
  • .claude-plugin/marketplace.json: groups published skills in the interactive skills CLI installer. Every skill must appear in exactly one group.
  • scripts/: the eval dataset validator and the trigger-eval runner.
  • .agents/skills/ and .claude/skills/: third-party skills installed locally for authoring (skill-creator, humanizer). Gitignored; tracked in skills-lock.json and restored with npx skills experimental_install (or npm run skills:restore).

Working on skills

  • One skill per delivery concern; kebab-case folder names prefixed with sg-gov- (the name frontmatter matches the folder).
  • Use the skill-creator skill to scaffold and iterate; validate with npm run skills:validate -- skills/<skill-name>.
  • Task-performance scenarios live in skills/<skill-name>/evals/evals.json; description-trigger queries live separately in skills/<skill-name>/evals/trigger-evals.json.
  • Validate every skill's task and trigger datasets locally with npm run skills:evals:validate (each skill needs both files: at least two task scenarios, and 20 trigger queries split 10 positive / 10 negative).
  • Run description-trigger evals with npm run skills:eval -- <skill-name> (extra run_eval flags pass through, e.g. --runs-per-query 3); run with no args to list skills that have trigger sets. Trigger evals shell out to claude -p, so they consume real usage.
  • When adding a skill, also add it to the appropriate catalog table in README.md and installer group in .claude-plugin/marketplace.json.

Read the full file on GitHub · 20 lines

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.

  1. yesterday Changed · +19 tokens per session db7b805429ea
  2. 8d ago Changed · +1 lines · -26 tokens per session 0b662c41e1df
  3. 2mo ago First seen · 19 lines · 522 tokens per session scan A 54e5490b649b

Subscribe to this mod's changes

sg-gov-skills AGENTS.md is an instructions file published in the GitHub repository kyleoliveiro/sg-gov-skills (17 stars, last pushed 2d ago), licensed MIT. It adds 515 tokens to every session, about $0.0021 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-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,719 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,516 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 3,037 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,313 tokens