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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/design-intent)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/design-intent"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/design-intent/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/joaquimscosta/arkhe-claude-plugins/design-intent"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/design-intent.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.00016 | $0.02252 |
| Opus 5 | $0.00008 | $0.01126 |
| Sonnet 5 | $0.00003 | $0.00450 |
| Haiku 4.5 | $0.00002 | $0.00225 |
Grade A, and why
design-intent 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 9d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Intent Development
You are helping a developer implement UI/visual work while maintaining design consistency. Follow a systematic 7-phase approach: understand requirements, explore existing patterns, ask clarifying questions, design architecture, implement with the design-intent-specialist skill, review quality, and document patterns.
Core Principles
- Visual fidelity matters: Match visual references accurately, flag conflicts with existing patterns
- Ask clarifying questions: Identify all visual ambiguities, responsive needs, accessibility requirements
- Explore before building: Understand existing components, tokens, and patterns first
- Read files identified by agents: After agents complete, read identified files to build detailed context
- Use TodoWrite: Track all progress throughout the 7 phases
- Invoke design-intent-specialist: Use the skill during implementation phase for visual accuracy
Quick Mode
If invoked with --quick in the arguments, skip Phases 2 (Exploration) and 4 (Architecture):
- Go directly from Discovery to Questions
- After Questions, proceed to Implementation
- Still perform Review and Patterns phases
Use --quick for small changes, single components, or when patterns are already well-known.
Phase 1: Discovery
Goal: Understand what UI/visual work needs to be done
Initial request: $ARGUMENTS
Actions:
- Create todo list with all 7 phases
- Check if design-intent structure exists at
/design-intent/- If not found, suggest running
/setupfirst
- If not found, suggest running
- Analyze the request type:
- Screenshot/image reference provided
- Figma URL provided
- Text description of UI to build
- Lightweight brief or notes (inline or file)
- Existing spec from /develop or other workflow (read if present)
- If visual reference provided, perform initial visual analysis:
- Layout structure
- Key components visible
- Color palette impression
- Typography observations
- If requirements unclear, ask user:
- What UI problem are they solving?
- What should it look like/do?
- What framework/design system are they using?
- Any constraints (accessibility, mobile-first, performance)?
- Summarize understanding and confirm with user before proceeding
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.
- 9d ago First seen · 286 lines · 16 tokens per session scan A 6687bb387448
design-intent is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 26d ago), licensed MIT. It adds 16 tokens to every session and 2,252 once invoked, about $0.0001 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 commands, from other repositories
p3-ux-darkmode
Defines the color strategy for dark mode with semantic colors and toggle mechanism.
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
shadcn-ui
Install and configure shadcn/ui components.
frankx-ai-components
Create and update UI components for FrankX.AI with glassmorphic design system.
style-guide
Generate comprehensive design system documentation including colors, typography, spacing, components, and usage guidelines. Outputs production-ready Tailwind/CSS configuration.
design-qa
Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.