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/jpavley/meta-loop-iosWrote 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/jpavley/meta-loop-ios/ml-wireframe)<a href="https://agentmods.dev/commands/jpavley/meta-loop-ios/ml-wireframe"><img src="https://agentmods.dev/badge/commands/jpavley/meta-loop-ios/ml-wireframe/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/jpavley/meta-loop-ios/ml-wireframe"><img src="https://agentmods.dev/badge/commands/jpavley/meta-loop-ios/ml-wireframe.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.00020 | $0.01771 |
| Opus 5.5 | $0.00008 | $0.00708 |
| Sonnet 5.5 | $0.00004 | $0.00354 |
| Haiku 4.5 | $0.00002 | $0.00177 |
Grade A, and why
ml-wireframe 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta-Loop: Wireframe Review
Review a wireframe to ensure mutual understanding between developer and AI before specification creation.
Mode: Ask Mode (questions and feedback only, no generation)
Arguments
$ARGUMENTS: Path to wireframe image(s) to review- Can be a single image path or a directory containing multiple wireframes
- A directory loads all
*-wireframe.pngfiles in it - Examples:
specs/views/my-feature/main-view-wireframe.pngorspecs/views/my-feature/
Prerequisites
This skill implements Step 1.2 of the Meta-Loop process defined in skills/meta-loop-methodology/SKILL.md.
The developer should have already drawn the wireframe (Step 1.1) before invoking this review.
Workflow
Phase 1: Load Wireframes
-
Resolve the path:
- If
$ARGUMENTSis a directory, glob for*.png,*.jpg,*.jpegfiles - If
$ARGUMENTSis a file, load that single image - If no argument provided, ask the developer for the wireframe path
- If
-
Load each wireframe image using the Read tool
-
Check for reusable view wireframes:
- Scan for any elements that appear multiple times
- Note if separate view wireframes exist for reusable patterns
Phase 2: Analyze
Describe your understanding of the wireframe. Cover:
-
Layout Structure:
- Overall arrangement (vertical, horizontal, grid, etc.)
- Major sections and their relationships
- Spacing and alignment patterns
-
Views Identified:
- UI elements visible (buttons, text fields, lists, etc.)
- Reusable patterns that could be extracted as views
- Data display areas
-
Data Flow:
- What data is being displayed?
- What user inputs are expected?
- What state changes might occur?
-
Interactions:
- Tappable/clickable elements
- Navigation triggers
- Gestures implied
-
Codebase Patterns:
- Reference existing patterns from CLAUDE.md that apply
- Note any existing views that could be reused
- Identify architectural patterns that fit
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 · 236 lines · 20 tokens per session scan A c62437ea567b
ml-wireframe is a command published in the GitHub repository jpavley/meta-loop-ios (3 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 1,771 once invoked, about $0.0001 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 commands, from other repositories
add-accessibility
SwiftUI view'lara accessibility identifier ekle. "accessibility ekle", "identifier ekle", "test icin etiketle", "VoiceOver destegi ekle", "erisilebilirlik ekle" gibi isteklerde tetiklenir.
run-tests
Run tests, debug failures, or audit test quality (launches test-runner agent).
matilha-design
Design guidance via core heuristics, delegates to matilha-design-pack or matilha-ux-pack if installed.
audit
Smart audit selector - analyzes your project and suggests relevant audits.
optimize-build
Scan Xcode project for build performance optimizations.
profile
Run automated performance profiling via xctrace CLI (launches performance-profiler agent).