Borrowing it
Nothing to install: this file belongs to LE-VAI/designesy-org. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LE-VAI/designesy-org/main/AGENTS.mdgit clone --depth 1 https://github.com/LE-VAI/designesy-orgWrote 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/le-vai/designesy-org/agents-md)<a href="https://agentmods.dev/instructions/le-vai/designesy-org/agents-md"><img src="https://agentmods.dev/badge/instructions/le-vai/designesy-org/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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
designesy-org 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 6d 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.
What it actually says
Designesy Agent Rules
You are operating inside Designesy.
This is not a typical web project.
Designesy is design intelligence infrastructure.
Core Understanding
Designesy turns: sources → principles → contracts → tools → systems → better designed work
Do Not
- Do not generate generic AI SaaS layouts.
- Do not assume this is a normal startup project.
- Do not build UI before structure and contracts exist.
- Do not invent design systems without source or rationale.
- Do not treat Labs as a blog or gallery.
Always
- Start from purpose, context, and system role.
- Use contracts (DESIGN.md) before inventing decisions.
- Prefer structure over surface.
- Encode reusable rules instead of one-off styling.
- Separate observed facts from derived design decisions.
- Verify outputs when visual quality matters.
Workflow Expectation
- Understand the system layer (docs/designesy)
- Identify artifact type (contract, lab, review, system)
- Build structure first
- Then refine output
- Then verify
Output Standard
Work should feel:
- intentional
- structured
- system-aware
- non-generic
- extensible
If unsure, ask before proceeding.
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.
- 6d ago First seen · 49 lines · 249 tokens per session scan A 6a690e8ddfcd
designesy-org AGENTS.md is an instructions file published in the GitHub repository LE-VAI/designesy-org (0 stars, last pushed 3d ago), licensed MIT. It adds 249 tokens to every session, about $0.0012 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
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.
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).
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).
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.
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.