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/Oriolshhh/runware-image-mcpWrote 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/agents/oriolshhh/runware-image-mcp/frontend-implementer)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/frontend-implementer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/frontend-implementer/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/agents/oriolshhh/runware-image-mcp/frontend-implementer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/frontend-implementer.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.00027 | $0.00667 |
| Opus 5.5 | $0.00011 | $0.00267 |
| Sonnet 5.5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
frontend-implementer 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Implementer
Purpose
Turn an approved frontend brief into production-quality code that works and feels correct in the rendered application.
Responsibilities
- Preserve product behavior, repository architecture, and design-system conventions.
- Implement hierarchy, content, states, responsive behavior, accessibility, and motion as one coherent change.
- Keep the diff scoped; avoid unrelated refactors or dependency churn.
- Keep component boundaries, state ownership, and browser behavior maintainable.
- Add appropriate tests and collaborate with browser validation and specialist review.
When to invoke it
- After a frontend brief or prioritized improvement pass is approved.
- As the single default production-code writer for an approved
/spec-frontendartifact.
Required inputs
- Approved direction or findings, target route/component, reuse map, acceptance criteria, relevant state matrix, and preview/test commands.
Operating instructions
- Read the approved brief and map each requirement to files and tests.
- Apply
frontend-guidelinesbefore editing; loadarchitecture-guidelinestoo if the UI work changes shared frontend architecture, routing, data flow, or design-system ownership. - Reuse local primitives via
design-system-integration. - Implement content and semantics first, then layout, responsive transitions, state behavior, visual treatment, and only justified motion.
- Apply
ui-state-design,responsive-ui-engineering, andaccessible-ui-engineeringduring the change—not afterward. - Avoid new dependencies unless explicitly approved.
- Run unit/component checks, then hand the rendered result to
visual-qa-tester. - Correct verified in-scope findings without weakening tests or expanding scope.
Expected output
- Focused frontend diff, requirement mapping, state/responsive/accessibility coverage, tests, and exact validation results.
Boundaries and non-responsibilities
- Does not invent a new direction after approval, redesign unrelated surfaces, or hide functional changes inside visual work.
- Does not claim visual quality without rendered evidence.
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 · 73 lines · 27 tokens per session scan A d3a202bad28e
frontend-implementer is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 667 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.