loop-frontend-implementation

loop-frontend-implementation is a command for Cursor from Oriolshhh/runware-image-mcp. It costs 0 tokens per session (469 once invoked), scanned A, original, MIT.

A guided workflow for designing and building a new frontend interface with a reusable design system and browser-based validation.

In plain words
What is it for?
Use it to map existing design tokens and components, plan the interface, get approval for material decisions, build the surface, and validate it in a browser.
Why use it?
It clarifies the visual direction, responsive behavior, interaction states, and approval points before implementation begins.

Command for Cursor

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.

agentmods
npx agentmods add commands/oriolshhh/runware-image-mcp/loop-frontend-implementation
Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Cursor.

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 loop-frontend-implementation

README.md
[![agentmods](https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-frontend-implementation.svg)](https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-frontend-implementation)
Your own site
<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-frontend-implementation"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-frontend-implementation.svg" alt="Measured on agentmods" 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 469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00000 $0.00469
Opus 5 $0.00000 $0.00234
Sonnet 5 $0.00000 $0.00094
Haiku 4.5 $0.00000 $0.00047

Measured today against content hash c6245337e84c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

loop-frontend-implementation 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 today.

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.

.cursor/commands/loop-frontend-implementation.md · 37 lines

What it actually says

/loop-frontend-implementation — Brief, design direction, approval, implementation, browser validation, and independent review.

Follow this ordered workflow. Respect every human-approval gate and stop when instructed.

name: frontend-implementation
description: Design and build a new frontend surface with browser-backed quality evidence.
max_iterations: 3
steps:
  - name: orient
    instruction: Reuse repository context; normalize the user, task, surface, constraints, content, success criteria, preview, and test setup.
  - name: system-map
    agent: design-system-specialist
    instruction: Map reusable tokens, primitives, components, themes, stories, and frontend conventions before proposing new ones.
  - name: direction
    agent: frontend-design-lead
    instruction: Produce one planning-only, brief-specific direction, complete state/responsive contract, acceptance rubric, and smallest implementation plan without recursively invoking the end-to-end /frontend-design command.
  - name: approve-material-decisions
    instruction: Wait for explicit approval only when brand, navigation, product behavior, shared design-system APIs, or dependencies materially change.
    gate: human-approval-when-required
  - name: implement
    agent: frontend-implementer
    instruction: Implement the approved direction with complete states, responsive behavior, accessibility, tests, and no unapproved dependencies.
  - name: browser-verify
    agent: visual-qa-tester
    instruction: Exercise the real UI across representative states and viewports; compare acceptance evidence and inspect console/network/runtime behavior.
  - name: specialist-review
    instruction: Run independent accessibility review and motion review when motion changed; return only verified in-scope blockers.
  - name: gates-and-decide
    instruction: Run configured gates; stop on acceptance, otherwise repeat only for an in-scope correction below max_iterations.
    gate: gates/default.yml

Apply context-discovery before broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read .agent/context/routing.md, load only relevant summaries, and verify critical claims against source.

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. today First seen · 37 lines · 0 tokens per session scan A c6245337e84c

Subscribe to this mod's changes

loop-frontend-implementation is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 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-03.