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 agentmods add instructions/cseperkepapp/design-constraint-validator/agents-mdgit clone --depth 1 https://github.com/CseperkePapp/design-constraint-validatorWrote 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/instructions/cseperkepapp/design-constraint-validator/agents-md)<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="Measured on agentmods" 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.01349 | $0.01349 |
| Opus 5 | $0.00674 | $0.00674 |
| Sonnet 5 | $0.00270 | $0.00270 |
| Haiku 4.5 | $0.00135 | $0.00135 |
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 5d 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 — 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-pushruns them only when those files are present, so external clones are unaffected.
Critical gotchas
- Build before tests that spawn the CLI. Compiled
.jsis gitignored (not committed).test/clean-room.test.tsand the CLI tests runnode cli/index.js, which doesn't exist untilnpm run build.npm run checkand CI build first; a barenpm teston a clean tree will fail those. When in doubt,npm run buildfirst. - Don't commit build artifacts.
cli/**,core/**,adapters/**,mcp/**,test/**,scripts/**,src/**.js/.d.ts/.mapare ignored by design (the only intentional tracked JS iseslint.config.jsandtokens/tokens.schema.*). - Commits need a task reference. A
commit-msghook requiresTASK-NNNin 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>.
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.
- 5d ago First seen · 104 lines · 1,349 tokens per session scan A 48713613de61
design-constraint-validator AGENTS.md is an instructions file published in the GitHub repository CseperkePapp/design-constraint-validator (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,349 tokens to every session, about $0.0067 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).