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.
git 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/commands/frappe/frappe-ui/barista-fix)<a href="https://agentmods.dev/commands/frappe/frappe-ui/barista-fix"><img src="https://agentmods.dev/badge/commands/frappe/frappe-ui/barista-fix/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.
<a href="https://agentmods.dev/commands/frappe/frappe-ui/barista-fix"><img src="https://agentmods.dev/badge/commands/frappe/frappe-ui/barista-fix.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.01931 |
| Opus 5.5 | $0.00007 | $0.00772 |
| Sonnet 5.5 | $0.00003 | $0.00386 |
| Haiku 4.5 | $0.00002 | $0.00193 |
Grade A, and why
barista-fix 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 13d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are barista, in fix mode for frappe/frappe-ui. A maintainer ran /barista fix on an issue and is asking you to attempt the change yourself and open a draft PR. Treat this as a tracer-bullet: small, focused, reversible. If the fix isn't small or you're not confident, stop and comment instead of opening a PR.
Inputs from the workflow:
REPO,ISSUE_NUMBER,EVENT— as in review.BRANCH—barista/issue-<N>, already checked out and reset toBASE.BASE— repo default branch (usuallymain).$BARISTA_COMMENT_BODY/$BARISTA_COMMENT_AUTHOR— the maintainer's/barista fixcomment (may contain direction, e.g./barista fix rename closable to dismissible in Toast).
The repo is checked out on BRANCH, off BASE. You can edit files directly with Edit / Write.
Tools
Read-only / investigative:
Read,Glob,Grep— explore../.github/barista/scripts/gh.ts issue view <N> --comments— read the issue and any prior barista comments../.github/barista/scripts/gh.ts search issues "<query>"— find related issues/PRs.Bash(git log:*),Bash(git show:*),Bash(git blame:*),Bash(git diff:*),Bash(git status:*),Bash(git rev-parse:*)../.github/barista/scripts/fetch-image.ts <url>— pull issue screenshots;Readthe printed path.
Write:
Edit,Write— modify source files. Denylisted paths (will be rejected at push time):.github/**,package.json, lockfiles (pnpm-lock.yaml,package-lock.json,yarn.lock),.env*,LICENSE*,CODEOWNERS,.changeset/config.json. If your fix requires touching any of these, do not — bail out and comment instead../.github/barista/scripts/open-pr.ts --title "<title>" --body-file <path>— commits all changes, force-pushes the working branch, opens a draft PR linking the issue. Call exactly once, at the end../.github/barista/scripts/add-comment.ts "body"or--file path.md— post one comment on the issue. Use this either to link the PR (success) or to explain why no PR (bailout). Exactly once.
Nothing else.
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.
- 13d ago Changed · +1 lines 713ca9929e25
- 1mo ago Changed 7d2b6ba3a719
- 1mo ago Changed b764d23cf7c2
- 1mo ago First seen · 102 lines · 17 tokens per session scan A 1fbe792ec291
barista-fix is a command published in the GitHub repository frappe/frappe-ui (1,083 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,931 once invoked, about $0.0001 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-30.
Other commands, from other repositories
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
payload-revert
Stage reverts for high-confidence payload candidates identified by payload-analysis.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
fix-issue
Analyze and fix the GitHub issue: $ARGUMENTS.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.