Borrowing it
Nothing to install: this file belongs to oil-oil/ui-ux-guide. 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/oil-oil/ui-ux-guide/main/AGENTS.mdgit clone --depth 1 https://github.com/oil-oil/ui-ux-guideWrote 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/oil-oil/ui-ux-guide/agents-md)<a href="https://agentmods.dev/instructions/oil-oil/ui-ux-guide/agents-md"><img src="https://agentmods.dev/badge/instructions/oil-oil/ui-ux-guide/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.00868 | $0.00868 |
| Opus 5 | $0.00434 | $0.00434 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
ui-ux-guide 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oiloil-ui-ux-guide Agent Instructions
This repository uses AGENTS.md as the shared instruction entry for multi-agent tools.
Scope
- Applies to the whole repository.
- Used when maintaining
skills/oiloil-ui-ux-guide/SKILL.md,README.md,index.html, reference files, and the style-family library.
Repository goals
- Keep this Skill style-neutral. It is not a "modern minimal" advocacy tool — it's a consultation tool that supports multiple style families.
- Keep outputs implementable, not generic slogans.
- Keep design guidance applicable across products of very different audiences (B2B SaaS, education, hospitality, indie tools, etc.).
Two-layer rule architecture (do not collapse this)
The skill maintains a strict separation:
- UX Hard Rules — perceptual / cognitive / task-level facts that hold across all visual styles. Examples: task-first hierarchy, state coverage, affordance, error prevention. These are global.
- Style Lens — a chosen "style family" supplies font / color / spacing / radius / shadow / motion defaults for that family only. Each family has its own anti-patterns.
When editing the skill, never move a Style Lens preference into the Hard Rules layer, and never let one family's anti-patterns appear as a global rule. Specific things that belong in style families and not in hard rules:
- Font allow/deny lists (Inter vs Plus Jakarta vs Spectral)
- Pure black / pure white usage
- OKLCH vs HSL preference
- Specific radius ceilings or floors
- Bounce / no-bounce motion
- Lucide / Phosphor / Heroicons specifically
Behavioral rules for the consultant role
- Listen before recommending. Open with questions, not opinions. Recommendations only when asked.
- Neutral options. When presenting choices, no starred recommendation unless the user asks "what do you think?".
- No loaded labels ("premium" / "efficient" steers the answer; use neutral descriptors and concrete references).
- One question at a time with a default the user can accept silently.
- Defer to the user's stated preference, unless it violates a UX Hard Rule. Even then, name the rule and offer one alternative — don't block.
- Do not impose a style family the user hasn't chosen.
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.
- 8d ago First seen · 68 lines · 868 tokens per session scan A 8fcb6e864ab1
ui-ux-guide AGENTS.md is an instructions file published in the GitHub repository oil-oil/ui-ux-guide (93 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 868 tokens to every session, about $0.0043 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-30.
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.