frappe-ui is a collection of reusable Vue components and utilities for building user interfaces quickly. It is for developers creating interfaces with Frappe and Vue.
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/frappe/frappe-ui/copilot-instructionsgit clone --depth 1 https://github.com/frappe/frappe-uiWrote 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/frappe/frappe-ui/copilot-instructions)<a href="https://agentmods.dev/instructions/frappe/frappe-ui/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/frappe/frappe-ui/copilot-instructions.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.00621 | $0.00621 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
frappe-ui copilot-instructions.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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frappe-ui Copilot instructions
frappe-ui is a Vue 3 component library and utilities package for Frappe-based apps. Treat it as a reusable library, not an app codebase.
Read order
CONTEXT.md— repo map and shared vocabulary.PHILOSOPHY.md— API design rules.spec/README.md— current specs and ADR index.- The relevant
spec/*.mdfile before changing public component APIs. v1-release/README.mdfor release execution, migration, changelog, and research.
If docs conflict, prefer:
spec/*.md > accepted ADRs > PHILOSOPHY.md > CONTEXT.md > v1-release research/plan
Working rules
- Preserve backwards compatibility unless a spec explicitly calls for a breaking v1 change or deprecation path.
- Prefer small, focused changes over broad rewrites.
- New or modernized Vue components should use TypeScript and
<script setup lang="ts">. - Public component APIs need typed props/emits/slots/exposed surfaces and useful JSDoc.
- Use semantic Tailwind tokens (
surface-*,ink-*,outline-*) instead of hardcoded colors. - Prefer stable styling hooks (
data-slot,data-state,data-size,data-variant,data-disabled) over DOM/class assumptions. - Accessibility, keyboard behavior, focus management, and ARIA semantics are part of done.
- Update docs, stories, tests, and changelog/migration notes when public behavior changes.
Component API rules
Follow PHILOSOPHY.md and the relevant spec.
Area-specific pointers
- Selection/menu:
spec/selection.md - Dialog:
spec/dialog.md - Inputs:
spec/inputs.md - Date/time pickers:
spec/date-picker.md - Toast:
spec/toast.md - ADR status:
spec/adr/README.md - v1 release execution:
v1-release/
Do not
- Invent new public API vocabulary without checking
PHILOSOPHY.mdandspec/. - Treat
v1-release/research/as the current contract. - Expand legacy compatibility APIs casually.
- Make broad repo-wide refactors unless explicitly requested.
- Optimize for app-local convenience at the expense of reusable-library stability.
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 · 56 lines · 621 tokens per session scan A 091bf4fd7f38
frappe-ui copilot-instructions.md is an instructions file published in the GitHub repository frappe/frappe-ui (1,010 stars, last pushed yesterday), licensed MIT. It adds 621 tokens to every session, about $0.0031 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
balsa-ui AGENTS.md
Instructions for pedrobalsa/balsa-ui, a project described as: Agent-native, open-code Vue/React components with independent palettes, themes, and gradient backgrounds.
tiptap tiptap.instructions.md
Instructions for ueberdosis/tiptap, covering tiptap, what is tiptap, repository layout, npm scripts and linting & formatting.
tiny-vue AGENTS.md
AGENTS.md instructions for opentiny/tiny-vue, covering agents.md, 项目概述, 关键目录结构, 环境要求 and 核心命令.
formkit CLAUDE.md
Instructions for formkit/formkit, covering formkit, architecture, packages, core (framework-agnostic) and vue integration.
waynboot-mobile AGENTS.md
Instructions for wayn111/waynboot-mobile, covering 仓库开发指南 (repository guidelines), 1. 核心技术栈与架构, 目录结构规范, 2. 开发、测试与构建命令 and 3. 编码风格与规范.
waynboot-mobile CLAUDE.md
Instructions for wayn111/waynboot-mobile, covering claude.md, 项目简介, 常用命令, 安装依赖 and 本地开发（端口 4949）.