Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/samzong/agent-brains/source-faithful-dify-prototype)<a href="https://agentmods.dev/skills/samzong/agent-brains/source-faithful-dify-prototype"><img src="https://agentmods.dev/badge/skills/samzong/agent-brains/source-faithful-dify-prototype.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.00089 | $0.01428 |
| Opus 5 | $0.00044 | $0.00714 |
| Sonnet 5 | $0.00018 | $0.00286 |
| Haiku 4.5 | $0.00009 | $0.00143 |
Grade A, and why
source-faithful-dify-prototype 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source-Faithful Dify Prototype
Purpose
Use this skill to create or update Dify prototype screens in:
/Users/x/git/lg/dify-prototype
The goal is not generic UI design. The goal is to build Dify prototypes that are either:
- Existing Screen Clone: source-faithful versions of existing Dify pages.
- New Feature Prototype: Dify-native prototypes for proposed features using Dify source patterns.
Existing screens should match Dify as closely as practical. New features should not claim official fidelity when Dify has no page yet; they must still use Dify components, tokens, layout patterns, and interaction language.
Required Start
Before creating or updating a screen:
cd /Users/x/git/lg/dify-prototype
pnpm sync:dify
Do not assume a local Dify repo. Do not add sync flags or alternate sync modes unless the user explicitly asks.
Read .dify-source.json after sync and remember the upstream commit for the final report.
Source Lookup
Find the nearest Dify source before implementing.
Common mappings:
- Login / sign-in:
dify-source/web/app/signin - Header / main nav:
dify-source/web/app/components/header - Sidebar shells:
dify-source/web/app/components/app-sidebar - Studio / apps list:
dify-source/web/app/components/apps - App detail / app surfaces:
dify-source/web/app/components/app - Knowledge list:
dify-source/web/app/components/datasets/list - Knowledge creation:
dify-source/web/app/components/datasets/create - Dataset documents/detail:
dify-source/web/app/components/datasets/documents - Hit testing:
dify-source/web/app/components/datasets/hit-testing - Workflow:
dify-source/web/app/components/workflow - Tags:
dify-source/web/features/tag-management - English copy:
dify-source/web/i18n/en-US
When the user says knowledgebase, knowledge base, or 知识库, map it to Dify datasets.
Implementation Rules
- Use
@langgenius/dify-ui/*primitives when available. - Do not hand-roll visible native form controls when Dify has a primitive. Map common controls first to:
@langgenius/dify-ui/selectfor select/listbox UI.@langgenius/dify-ui/inputfor text inputs.@langgenius/dify-ui/sliderfor Top K, temperature, score, and weight sliders.@langgenius/dify-ui/checkboxfor checkbox lists and multi-select rows.@langgenius/dify-ui/switchfor on/off parameter toggles.@langgenius/dify-ui/number-field,radio-group,popover, anddropdown-menuwhen the source surface uses them.
- Native
<select>,<textarea>,input[type="checkbox"],input[type="range"], and plain text inputs are allowed only when Dify source uses that exact native control or when they are hidden/internal backing inputs generated by Dify/Base UI primitives. - Use synced Dify tokens, themes, Tailwind classes, icons, and assets.
- Use Dify icon systems:
i-ri-*,i-custom-*,@remixicon/react, and synced SVG components. - Put prototype code, adapters, fixtures, and local state in
apps/prototype. - Do not edit synced upstream mirrors under
dify-source/or synced packages unless the user explicitly asks to change the sync project itself. - Mock backend data locally. Do not present mocked backend behavior as real.
- Do not invent Dify styling when source has an equivalent.
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 · 135 lines · 89 tokens per session scan A a66b93f44bfd
source-faithful-dify-prototype is a skill published in the GitHub repository samzong/agent-brains (6 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 1,428 once invoked, about $0.0004 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 skills, from other repositories
web-prototype
General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed assets/template.html and pasting section layouts from references/layouts.md. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.
velar-luxury-real-estate
Use this plugin when the user wants a high-end luxury real-estate / architecture landing page with cinematic scroll choreography: a typewriter preloader that lifts away, a scroll-driven house image that rises from below and scales up while pinning to a dark statement section, a sticky dark stats band with count-up…
web-prototype-taste-brutalist
Swiss industrial-print web prototype. Newsprint canvas, monolithic black grotesque, viewport-bleeding numerals, hairline grid dividers, hazard-red accent, ASCII syntax decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Swiss Industrial Print mode).
web-prototype-taste-soft
Apple-tier soft web prototype. Silver/cream canvas, double-bezel cards, button-in-button CTAs, generous squircle radii, spring motion, ambient mesh. Distilled from Leonxlnx/taste-skill soft-skill + sections 4–8 of taste-skill.
mockup-device-3d
Static iPhone and MacBook 3D-style showcase with real HTML embedded on screens, glass-lens refraction, and 360-degree turntable composition.
web-prototype-taste-editorial
Editorial-minimalist web prototype. Warm monochrome canvas, serif display + grotesque body, 1px hairline borders, muted pastel chips, generous macro-whitespace, ambient micro-motion. Distilled from Leonxlnx/taste-skill minimalist-skill.