multi-platform

multi-platform is a command for Claude Code from HermeticOrmus/LibreUIUX-Claude-Code. It costs 0 tokens per session (1,898 once invoked), scanned A, original, MIT.

A workflow for building one feature across web, mobile, and desktop applications. It starts with shared API contracts and data models so each platform can be developed in parallel while keeping behavior aligned.

In plain words
What is it for?
Use it to plan cross-platform features, define REST, GraphQL, or WebSocket interfaces, coordinate parallel implementation, and maintain feature parity.
Why use it?
It helps avoid different platforms implementing the same feature in incompatible ways. Shared contracts reduce integration problems while still allowing platform-specific adjustments.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to plan cross-platform features, define REST, GraphQL, or WebSocket interfaces, coordinate parallel implementation, and maintain feature parity.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hermeticormus/libreuiux-claude-code/multi-platform
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code

Made for: Claude Code.

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.

agentmods badge for multi-platform

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/multi-platform/github.svg)](https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/multi-platform)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/multi-platform"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/multi-platform/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.

agentmods 80×15 button for multi-platform

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/multi-platform"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/multi-platform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,898 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01898
Opus 5.5 $0.00000 $0.00759
Sonnet 5.5 $0.00000 $0.00380
Haiku 4.5 $0.00000 $0.00190

Measured 29d ago against content hash b56cc5b6a3f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multi-platform 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 29d 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.

plugins/multi-platform-apps/commands/multi-platform.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Multi-Platform Feature Development Workflow

Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.

[Extended thinking: This workflow orchestrates multiple specialized agents to ensure feature parity across platforms while maintaining platform-specific optimizations. The coordination strategy emphasizes shared contracts and parallel development with regular synchronization points. By establishing API contracts and data models upfront, teams can work independently while ensuring consistency. The workflow benefits include faster time-to-market, reduced integration issues, and maintainable cross-platform codebases.]

Phase 1: Architecture and API Design (Sequential)

1. Define Feature Requirements and API Contracts

  • Use Task tool with subagent_type="backend-architect"
  • Prompt: "Design the API contract for feature: $ARGUMENTS. Create OpenAPI 3.1 specification with:
    • RESTful endpoints with proper HTTP methods and status codes
    • GraphQL schema if applicable for complex data queries
    • WebSocket events for real-time features
    • Request/response schemas with validation rules
    • Authentication and authorization requirements
    • Rate limiting and caching strategies
    • Error response formats and codes Define shared data models that all platforms will consume."
  • Expected output: Complete API specification, data models, and integration guidelines

2. Design System and UI/UX Consistency

  • Use Task tool with subagent_type="ui-ux-designer"
  • Prompt: "Create cross-platform design system for feature using API spec: [previous output]. Include:
    • Component specifications for each platform (Material Design, iOS HIG, Fluent)
    • Responsive layouts for web (mobile-first approach)
    • Native patterns for iOS (SwiftUI) and Android (Material You)
    • Desktop-specific considerations (keyboard shortcuts, window management)
    • Accessibility requirements (WCAG 2.2 Level AA)
    • Dark/light theme specifications
    • Animation and transition guidelines"
  • Context from previous: API endpoints, data structures, authentication flows
  • Expected output: Design system documentation, component library specs, platform guidelines

Read the full file on GitHub · 181 lines

Changes

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.

  1. 29d ago First seen · 181 lines · 0 tokens per session scan A b56cc5b6a3f9

Subscribe to this mod's changes

multi-platform is a command published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,898 tokens. 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-09-20.