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.
git clone --depth 1 https://github.com/eagonmeng/sync-blankWrote 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/rules/eagonmeng/sync-blank/concept-state-specification)<a href="https://agentmods.dev/rules/eagonmeng/sync-blank/concept-state-specification"><img src="https://agentmods.dev/badge/rules/eagonmeng/sync-blank/concept-state-specification/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/rules/eagonmeng/sync-blank/concept-state-specification"><img src="https://agentmods.dev/badge/rules/eagonmeng/sync-blank/concept-state-specification.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.00014 | $0.02621 |
| Opus 5.5 | $0.00006 | $0.01048 |
| Sonnet 5.5 | $0.00003 | $0.00524 |
| Haiku 4.5 | $0.00001 | $0.00262 |
Grade A, and why
concept-state-specification 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 1mo 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Simple State Form (SSF) is a syntax for data modeling that is designed to be both easy to read (especially by non-technical people) and also easily translatable into a formal database schema (either by an LLM or by a conventional parser). It is intended to be compatible with collection databases (such as MongoDB), relational databases (such as SQLLite), relational modeling languages (such as Alloy), and also graph databases (such as Neo and GraphQL). SSF was motivated by the need for a simple language for state declarations for concepts in concept design.
Semantic Features
The key semantic features of SSF are: the ability to declare sets of objects, along with relations that map them to other objects or primitive values, and subsets of these sets, with additional relations. A basic set of primitive types is provided, as well as enumerations. The language is first-order, so an object can be mapped to a set of objects or scalars, but not to a set of sets. Union types are currently not supported.
Grammar
- schema ::= ( set-decl | subset-decl )*
- set-decl ::= [ "a" | "an" ] ("element" | "set") [ "of" ] object-type [ "with" field-decl + ]
- subset-decl ::= [ "a" | "an" ] sub-type ("element" | "set") [ "of" ] ( object-type | sub-type ) [ "with" field-decl + ]
- field-decl ::= [ "a" | "an" ] ["optional"] [field-name] (scalar-type | set-type)
- scalar-type ::= object-type | parameter-type | enumeration-type | primitive-type
- set-type ::= ("set" | "seq" ) [ "of" ] scalar-type
- enumeration-type ::= "of" (enum-constant "or" )+ enum-constant
Grammar conventions
- [ x ] means x is optional
- In ( x ), the parens used for grouping, and do not appear in the actual language
- a | b means either a or b
- x * means an iteration of zero or more of x
- x + means an iteration of one or more of x
Grammar constraints
- A field-name may be omitted only for declaring a field of object-type or parameter-type. Omitting the field name is equivalent to including a name that is the same as the name of the type but with the first character in lower case.
- The hierarchy that is specified by subset-decls cannot contain cycles. Thus, a subset-decl may not, for example, declare a subset with a sub-type that is the same as the sub-type that it is a subset of.
- The field-names within a set-decl or subset-decl must be unique. Also, within all the decls that are in the hierarchy beneath a set-decl, field-names must be unique.
- A field-decl that has a set-type cannot use the optional keyword.
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.
- 1mo ago First seen · 279 lines · 14 tokens per session scan A 06fc3dd5a39c
concept-state-specification is a cursor rule published in the GitHub repository eagonmeng/sync-blank (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,621 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
sync-timedb-archive-janitor-contract
Day-close / cold-path worker contracts for synctimedb (A invariants; B tick coordinator retired).
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.