What is design-constraint-validator AGENTS.md?

A set of working instructions for contributors and coding agents in the design-constraint-validator repository. The project is a command-line tool and library that checks design tokens, such as colors and type scales, against mathematical and accessibility rules.

Use it when working on this repository. It covers setup, building, testing, linting, type checking, the full validation command, and the rule to use one branch per task.

It explains the repository's commands, important files, and workflow conventions so changes can be made and checked consistently.

How CseperkePapp/design-constraint-validator configures Codex and Open

Reuse

Borrowing it

Nothing to install: this file belongs to CseperkePapp/design-constraint-validator. 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/CseperkePapp/design-constraint-validator/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/CseperkePapp/design-constraint-validator

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/cseperkepapp/design-constraint-validator/agents-md/github.svg)](https://agentmods.dev/instructions/cseperkepapp/design-constraint-validator/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/cseperkepapp/design-constraint-validator/agents-md"><img src="https://agentmods.dev/badge/instructions/cseperkepapp/design-constraint-validator/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/cseperkepapp/design-constraint-validator/agents-md"><img src="https://agentmods.dev/badge/instructions/cseperkepapp/design-constraint-validator/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,349 This file is loaded in full into every session.

When invoked 1,349 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.

Model	Per session	Once invoked
Fable 5.1	$0.01349	$0.01349
Opus 5.5	$0.00540	$0.00540
Sonnet 5.5	$0.00270	$0.00270
Haiku 4.5	$0.00135	$0.00135

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

Security

Grade A, and why

design-constraint-validator 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 · 104 lines

How it starts

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

AGENTS.md — working in this repo

Onboarding for AI coding agents (Claude, Codex, etc.). Read this first; it saves you from rediscovering the conventions every session. Human contributors: see CONTRIBUTING.md.

What DCV is

design-constraint-validator (DCV) is a CLI + library that validates design tokens against mathematical constraints — WCAG contrast (with alpha compositing), monotonic type/lightness scales, thresholds, cross-axis rules. The engine math lives in core/ and is verified; treat core/color.ts and core/constraints/* as load-bearing.

Commands

npm ci                  # install (CI uses --ignore-scripts)
npm run build           # tsc → emits .js/.d.ts next to sources
npm test                # vitest (excludes compiled **/*.test.js)
npm run lint            # eslint
npm run typecheck       # tsc --noEmit
npm run check           # typecheck + lint + build + test (the full gate)

Task-ledger integrity checks live in the maintainer's local-only workflow-automation system (src/, scripts/ — gitignored) and are not part of the public gate. The tracked .githooks/pre-push runs them only when those files are present, so external clones are unaffected.

Critical gotchas

Build before tests that spawn the CLI. Compiled .js is gitignored (not committed). test/clean-room.test.ts and the CLI tests run node cli/index.js, which doesn't exist until npm run build. npm run check and CI build first; a bare npm test on a clean tree will fail those. When in doubt, npm run build first.
Don't commit build artifacts. cli/**, core/**, adapters/**, mcp/**, test/**, scripts/**, src/** .js/.d.ts/.map are ignored by design (the only intentional tracked JS is eslint.config.js and tokens/tokens.schema.*).
Commits need a task reference. A commit-msg hook requires TASK-NNN in the message (or an escape tag like [no-task: …]). Hooks live in .githooks (git config core.hooksPath .githooks).
End commit messages with the project co-author line, e.g. Co-Authored-By: <model> <noreply@<provider>.com>.

Read the full file on GitHub · 104 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.

2mo ago First seen · 104 lines · 1,349 tokens per session scan A 48713613de61

Subscribe to this mod's changes

design-constraint-validator AGENTS.md is an instructions file published in the GitHub repository CseperkePapp/design-constraint-validator (0 stars, last pushed 4mo ago), licensed MIT. It adds 1,349 tokens to every session, about $0.0054 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.

Design and UX

design-constraint-validator AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-constraint-validator AGENTS.mdCseperkePapp/design-constraint-validator	Instructions file	0	4mo ago	MIT	A	1,349	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

design-constraint-validator: Instructions file for Codex