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 skills add Biraj2004/huashu-skills-english --skill huashu-design-engit clone --depth 1 https://github.com/Biraj2004/huashu-skills-englishWrote 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/biraj2004/huashu-skills-english/huashu-design-en)<a href="https://agentmods.dev/skills/biraj2004/huashu-skills-english/huashu-design-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-design-en/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/skills/biraj2004/huashu-skills-english/huashu-design-en"><img src="https://agentmods.dev/badge/skills/biraj2004/huashu-skills-english/huashu-design-en.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.00057 | $0.16633 |
| Opus 5.5 | $0.00023 | $0.06653 |
| Sonnet 5.5 | $0.00011 | $0.03327 |
| Haiku 4.5 | $0.00006 | $0.01663 |
Grade A, and why
huashu-design 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.
How it starts
The opening of the file, as written. The whole thing — 1,538 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Philosophy Consultant
Understand requirements like a top design agency — recommend design philosophy directions, generate AI prompts, and conduct expert-level reviews.
Core Principles
- Constrain philosophy, not form — Define "why design this way", not "what it looks like"
- Deep understanding first — Understand what the user truly wants to communicate before recommending a style
- Design is probabilistic — Good constraints produce diverse, high-quality results
- Review like a perfectionist — High standards, but always provide an actionable path forward
When This Skill Triggers
Before design (Design Direction) — Any output that involves visual presentation:
- Websites / landing pages / brand sites, app interfaces / prototypes
- PPT / Keynote, PDF reports / white papers
- Infographics / posters / illustrations / covers
After design (Design Critique) — Automatically initiates a review once a visual design output is complete.
Workflow: Before Design (Phases 1–6)
Phase 1: Deep Understanding of Requirements
- Questions: Target audience / Core message / Emotional tone / Output format
- Maximum 3 questions at once; skip if requirements are already clear
Phase 2: Consultative Restatement (100–200 words)
- Restate the core requirements, audience, scenario, and emotional tone in your own words
- Close with: "Based on this understanding, I've prepared 3 design directions for you"
Phase 3: Recommend 3 Design Philosophies
Each direction includes:
| Element | Explanation |
param($m)
$inner = $m.Groups[1].Value
# Split by | and fix each cell separator
$cells = $inner -split '\|'
$fixedCells = $cells | ForEach-Object {
$cell = ---
name: huashu-design description: Design philosophy consultant — recommends 3 directions from 20 styles, generates visual demos, and AI prompts. Use when the user mentions "design style", "design direction", "colour palette", "visual style", "design review", or "recommend a style".
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 1,538 lines · 57 tokens per session scan A 7147a839d931
huashu-design is a skill published in the GitHub repository Biraj2004/huashu-skills-english (3 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 16,633 once invoked, about $0.0002 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.
Other skills, from other repositories
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
user-research-synthesis
Analiza y sintetiza hallazgos de investigación de usuarios en insights estructurados y accionables. Úsalo cuando te proporcionen datos de investigación de usuarios, transcripciones de entrevistas, resultados de encuestas o feedback de usuarios que necesiten ser analizados y resumidos. Produce una síntesis temática con…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
architectural-programme-brief
Turn a client's wishes into an architectural brief that can actually be designed against — the accommodation schedule, the adjacencies, the budget reality, and the constraints named before they become change orders. Use when asked to write an architectural brief, prepare a project brief for a building, run a client…
architecture-client-presentation
Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options…