sct: Instructions file for Codex

AGENTS.md

sct AGENTS.md is an instructions file for Codex, OpenCode from neolee/sct. It costs 3,068 tokens per session, scanned A, original, MIT.

Project guidance for SCT, a native macOS app for configuring the Squirrel input method. It describes how the app reads base YAML settings and writes user changes as separate custom YAML patches.

In plain words
What is it for?
Understanding the two-layer configuration model, merged settings views, SwiftUI and Swift requirements, and YAML handling.
Why use it?
It helps agents preserve the input method's original settings while making user changes visible and reversible.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is neolee/sct's own configuration. It tells Codex and OpenCode how to work on sct 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 sct configures →

View source ↗ neolee/sct
Reuse

Borrowing it

Nothing to install: this file belongs to neolee/sct. 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/neolee/sct/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/neolee/sct

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 sct AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/neolee/sct/agents-md"><img src="https://agentmods.dev/badge/instructions/neolee/sct/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,068 This file is loaded in full into every session.
When invoked 3,068 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.03068 $0.03068
Opus 5.5 $0.01227 $0.01227
Sonnet 5.5 $0.00614 $0.00614
Haiku 4.5 $0.00307 $0.00307

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

Security

Grade A, and why

sct 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 2mo 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.

AGENTS.md · 181 lines

How it starts

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

Squirrel Configuration Tool (SCT) - Agent Guide

This document serves as a project overview and design record for AI agents working on the Squirrel (鼠须管) configuration GUI.

Project Overview

The goal is to provide a native macOS GUI for configuring the Squirrel input method, which traditionally requires manual editing of YAML files in ~/Library/Rime.

Core Design Philosophy

"Respect Rime Logic, Simplify User Operation"

  • Non-Destructive: Never modify default .yaml files. All changes must be written to .custom.yaml files under the patch: key.
  • Native Experience: Use SwiftUI and macOS design patterns to make configuration feel like a first-class system setting.
  • Transparency: Users should be able to see what YAML changes are being made.

Key Design Decisions

1. Dual-Layer Configuration Model

  • Base Layer: default.yaml, squirrel.yaml (Read-only).
  • Patch Layer: default.custom.yaml, squirrel.custom.yaml (Read/Write).
  • Merged View: The GUI displays the result of merging the Patch Layer into the Base Layer.

2. Technology Stack

  • Language: Swift 6.0+
  • Framework: SwiftUI (Targeting latest macOS)
  • YAML Engine: Yams for robust YAML parsing and serialization.
  • Markdown Engine: MarkdownUI for rich help documentation rendering.

3. Configuration Merging Logic

Rime's patch system supports:

  • Simple key-value replacement.
  • Nested key access (e.g., style/font_face).
  • Array manipulation (though SCT currently focuses on full array replacement for simplicity).

4. Color Handling

Rime uses BGR (Blue-Green-Red) hex format (e.g., 0xBBGGRR). SCT must:

  • Convert BGR to SwiftUI.Color for the UI.
  • Convert SwiftUI.Color back to BGR for saving.

Functional Modules

General Settings

  • menu/page_size: Number of candidates.
  • schema_list: Selection and ordering of input schemas.
  • ascii_composer: Behavior of Shift/Caps Lock keys.

Read the full file on GitHub · 181 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. 2mo ago First seen · 181 lines · 3,068 tokens per session scan A baba49d495e7

Subscribe to this mod's changes

sct AGENTS.md is an instructions file published in the GitHub repository neolee/sct (55 stars, last pushed 7mo ago), licensed MIT. It adds 3,068 tokens to every session, about $0.0123 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

sct AGENTS.md compared with instructions from other repositories

sct AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sct AGENTS.mdneolee/sctInstructions file557mo agoMITA3,068Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot