A workflow for implementing an approved software specification and checking the result with tests and project quality gates.

Use it to deliver approved features or fixes, including frontend work, backend changes, and image-related interface updates.

It ensures coding starts from an agreed plan and that the finished changes meet automated checks.

implement — Skill for Claude Code and Codex by Oriolshhh

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.

Any agent

npx skills add Oriolshhh/runware-image-mcp --skill implement

Clone the repo

git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/implement.svg)](https://agentmods.dev/skills/oriolshhh/runware-image-mcp/implement)

Your own site

<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/implement"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/implement.svg" alt="Measured on agentmods" height="20"></a>

Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,014 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01014
Opus 5	$0.00005	$0.00507
Sonnet 5	$0.00002	$0.00203
Haiku 4.5	$0.00001	$0.00101

Measured 3d ago against content hash 9b778d6b7cc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

implement 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 3d 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.

.agents/skills/implement/SKILL.md · 92 lines

How it starts

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

/implement — Implement an approved spec

Purpose

Deliver the approved spec with tests and green gates.

Invocation

/implement <spec name>

Accepted input

An approved spec under .agent/specs/.

Prerequisites

An approved spec. If none exists, run /spec first.

Procedure

Confirm an approved spec exists. If it declares work_type: frontend-redesign, hand it to /implement-spec-frontend; the generic path does not provide the required baseline comparison and independent visual-craft review. If it declares work_type: frontend-image-polish, require one explicitly approved tier, apply image-art-direction, generate only the listed assets through an available user-approved image tool/provider, preserve the spec's exact style lock and per-slot dimensions, then route integration to frontend-implementer and rendered comparison to visual-qa-tester.
Classify the approved tasks before implementation. For user-facing rendered UI work, route those tasks to frontend-implementer and apply frontend-guidelines, design-system-integration, ui-state-design, responsive-ui-engineering, and accessible-ui-engineering alongside minimal-diff, test-design, and code-quality-guidelines. Keep non-UI tasks with implementer.
If the frontend spec lacks an approved visual direction or makes material brand, navigation, interaction, or shared design-system decisions, stop and hand that scope to /frontend-design; do not invent the direction while coding.
Apply engineering guidelines by surface before editing:
- always apply code-quality-guidelines;
- apply architecture-guidelines for new abstractions, shared modules, APIs, data flow, refactors, migrations, or cross-boundary changes;
- apply backend-guidelines for server-side, CLI, persistence, validation, integrations, auth, jobs, or operational work;
- apply frontend-guidelines for rendered UI, components, routes, browser behavior, frontend state, or design-system work.
Implement the spec's dependency-ordered tasks with the smallest reasonable diff. Use motion-design only when motion is explicitly in scope or changed.
Add or update tests so the spec's test plan is satisfied. For rendered UI changes, hand the result to visual-qa-tester and apply browser-visual-validation; verify relevant states, viewports, keyboard/focus, zoom/reflow, reduced motion, and runtime console/network behavior.
Run the gates (install, lint, typecheck, test, build) and make them pass.
Summarize what changed, requirements satisfied, routing used, guidelines applied, browser evidence when applicable, and gates run.

Read the full file on GitHub · 92 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.

3d ago First seen · 92 lines · 11 tokens per session scan A 9b778d6b7cc0

Subscribe to this mod's changes

implement is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,014 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-09-03.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens