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 skills/lenxism/ives/elements-patternsnpx skills add lenxism/ives --skill elements-patternsgit clone --depth 1 https://github.com/lenxism/ivesWhat 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 | $0.00113 | $0.01110 |
| Opus 5 | $0.00056 | $0.00555 |
| Sonnet 5 | $0.00023 | $0.00222 |
| Haiku 4.5 | $0.00011 | $0.00111 |
Grade A, and why
elements-patterns 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elements & Patterns
Every element is a stepping stone in the user's journey from point A to point B. Design each one through the lens of that experience.
Read references/elements-knowledge.md for detailed guidance on specific element types.
Universal Principles
Start with platform defaults
Before designing any element from scratch, look at how iOS (HIG) or the web (shadcn/Tailwind) handles it. Match the convention, then exceed it.
Consistency over creativity
A consistent set of "good" components beats a mix of some "great" and some "mediocre." Every element should feel like it belongs to the same family.
State coverage
Every interactive element needs ALL states designed:
- Default, Hover, Focused/Active, Disabled, Error, Success, Loading
- Empty states for lists, search results, data views
- Skeleton/loading states for async content
Missing states is the fastest way to look amateur.
Navigation
- Mobile: Bottom tab bar for 3-5 primary destinations. More than 5? Reconsider information architecture.
- Web app: Sidebar for apps (collapsible), top bar for marketing sites.
- Highlight the active state clearly — color, weight, or indicator mark.
- Secondary navigation (settings, profile) can live in header icons rather than tabs.
- Test navigation labels at realistic lengths — "Activity" fits, "Transaction History" might not.
Input Fields
The mighty input needs extensive design work:
- Label: Top-aligned, 8px gap to field, same or slightly smaller size as input text
- Placeholder: AA-large contrast (3:1) minimum — dark enough to read, light enough to not look pre-filled
- Focus state: Unmistakable. 2px colored border is the standard.
- Error state: Red border + icon + message. Color alone isn't accessible.
- Helper text: Below the field, 2pt smaller than input text, AA contrast
- Sizing: Match field width to expected content. Zip code doesn't need a full-width field.
Input variants to design
Default, hover, focused, filled, error, success, disabled, password (with show/hide), multiline, dropdown, prefixed, character count, checkboxes, radio buttons, toggles.
What ships with it
1 file 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.
- 2d ago First seen · 105 lines · 113 tokens per session scan A 25144f22e320
elements-patterns is a skill published in the GitHub repository lenxism/ives (5 stars, last pushed 6mo ago), licensed MIT. It adds 113 tokens to every session and 1,110 once invoked, about $0.0006 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.