agentmods.dev

dryui: Instructions file for Codex

AGENTS.md

dryui AGENTS.md is an instructions file for Codex, OpenCode from rob-balfre/dryui. It costs 1,210 tokens per session, scanned A, original, MIT.

Repository instructions for AI coding agents working on DryUI, a project for reusable UI components, themes, and route patterns.

In plain words
What is it for?
Following project rules, finding the canonical files to edit, preserving the intended documentation structure, and running end-to-end checks.
Why use it?
They keep agents aligned with the repository’s official documentation, source files, design rules, accessibility policy, and testing process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex; mentions OpenCode.

This is rob-balfre/dryui's own configuration. It tells Codex and OpenCode how to work on dryui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dryui configures →

not rated 9repo 5mo ago A scan 1,210 tokens original MIT
View source ↗ rob-balfre/dryui dryui.dev
Reuse

Borrowing it

Nothing to install: this file belongs to rob-balfre/dryui. 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/rob-balfre/dryui/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rob-balfre/dryui

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.

agentmods badge for dryui AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rob-balfre/dryui/agents-md/github.svg)](https://agentmods.dev/instructions/rob-balfre/dryui/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rob-balfre/dryui/agents-md"><img src="https://agentmods.dev/badge/instructions/rob-balfre/dryui/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.

agentmods 80×15 button for dryui AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rob-balfre/dryui/agents-md"><img src="https://agentmods.dev/badge/instructions/rob-balfre/dryui/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,210 This file is loaded in full into every session.
When invoked 1,210 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01210 $0.01210
Opus 5.5 $0.00484 $0.00484
Sonnet 5.5 $0.00242 $0.00242
Haiku 4.5 $0.00121 $0.00121

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

Security

Grade A, and why

dryui 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 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.

AGENTS.md · 47 lines

How it starts

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

AGENTS.md

Repo-wide instructions for AI coding agents working in this repository.

Canonical Docs

Canonical Sources

  • Editor install snippets and MCP config examples live in apps/docs/src/lib/ai-setup.ts. Do not duplicate them elsewhere.
  • Public docs copy and positioning should match apps/docs/src/lib/site-meta.ts and the docs homepage: human-led, agent-assisted UI for reusable components, themes, and route patterns. Avoid positioning DryUI as a full automation tool, an "agent-built apps" product, or a Svelte-only message.
  • The public docs route surface is intentionally small: /, /getting-started, and /components/[slug]. Do not re-add removed exploration pages (/tools, /how-it-works, /how-we-work, /grid-rules, /theme-wizard, logo option pages, /components index pages, or similar samples) unless explicitly requested.
  • Skill sources live in top-level skills/ (dryui-build, dryui-feedback, dryui-live-feedback, dryui-init). One source of truth.
  • Recommended install path for end users: npx skills add rob-balfre/dryui (skills.sh standard).
  • bun run validate:skills lints every SKILL.md (frontmatter present, name=dirname, description length).
  • /plugins in this repo refers to the in-app Claude or Codex install flow (sunset for DryUI; users install via npx skills add rob-balfre/dryui), not a repo directory.

Repo Rules

  • DryUI is pre-alpha. Prefer the current shape over compatibility shims unless a task explicitly asks for backwards compatibility.
  • Use DryUI skills as the default entry point. For any DryUI component, route, template, styling, layout, docs, or feedback task, load the relevant top-level skills/*/SKILL.md before planning or editing files. If the task also involves Svelte or SvelteKit, load the dryui-build skill first, then use the Svelte MCP docs/autofixer flow.
  • Run the local feedback dashboard with bunx dryui-feedback (bin shipped from @dryui/feedback-server).
  • Use package-level lint/build/test commands for deterministic validation: component contracts, a11y, tokens, CSS discipline.
  • DryUI ships no layout component. Page/section structure lives as plain CSS Grid in root src/layout.css, scoped under [data-layout="<name>"]. The file is imported last from src/routes/+layout.svelte after DryUI theme CSS and ../app.css.
  • All display: grid and display: flex declarations in consumer code live in src/layout.css (or @container blocks within it). Mobile-first; @container queries for responsive shifts, never @media for layout breakpoints.
  • @dryui/lint has two build-time surfaces: dryuiLint() in svelte.config for component rules, and dryuiLayoutCss() in vite.config for src/layout.css. The Vite plugin must run in vite dev/HMR and vite build; missing src/layout.css is warning-only, violations are hard errors.
  • The docs shell header is centralized in apps/docs/src/routes/+layout.svelte: logo, search, GitHub, and theme toggle. Keep route pages focused on content and avoid duplicating header chrome.
  • The docs logo is the simple font-based DryUI wordmark in apps/docs/src/lib/components/Logo.svelte. The favicon lives at apps/docs/static/favicon.svg and should stay black and white with no underline.
  • Keep root-level Markdown durable. One-off audits, scratch TODOs, and generated reports belong under docs/, reports/, or ignored local directories, not the repo root.
  • Repo-local editor install output such as .agents/skills/, .github/skills/, .opencode/, and opencode.json is not canonical source.

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

  1. 1mo ago First seen · 47 lines · 1,210 tokens per session scan A 408a8aa22b0a

Subscribe to this mod's changes

dryui AGENTS.md is an instructions file published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 5mo ago), licensed MIT. It adds 1,210 tokens to every session, about $0.0048 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.

Claude CodeFrontendclaudecodexsveltesveltekitui
Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens