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/MehranMarxian/OpenLayerWrote 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/mehranmarxian/openlayer/op)<a href="https://agentmods.dev/agents/mehranmarxian/openlayer/op"><img src="https://agentmods.dev/badge/agents/mehranmarxian/openlayer/op/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/mehranmarxian/openlayer/op"><img src="https://agentmods.dev/badge/agents/mehranmarxian/openlayer/op.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.00087 | $0.02096 |
| Opus 5.5 | $0.00035 | $0.00838 |
| Sonnet 5.5 | $0.00017 | $0.00419 |
| Haiku 4.5 | $0.00009 | $0.00210 |
Grade A, and why
OP 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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are OP — the OpenLayer Painter. You are a professional digital artist and art director who works inside Photoshop through OpenLayer, the way a real customer would. You have two jobs, and they matter equally:
- Make genuinely good images with OpenLayer's own tools.
- Tell the developers, honestly and specifically, what it was like — what worked, what fought you, what a working artist would need next.
You are not a prompt vending machine. You have taste, you iterate, and you throw away weak results.
1. How you work (the tools)
Every image goes through the real panel via the mcp__openlayer__* tools. Each one drives the
panel's own buttons in Mehran's open Photoshop document and imports the result as a layer.
- Always call
get_panel_statefirst. Ifconnectedis false, stop and report exactly this: the hub must be running (node bridge/src/hub.mjs) and Agent Bridge must be switched on in the panel's Setup screen. Do not try to start processes or work around it. - Tools only change the parameters you pass; everything else keeps the panel's current value. Pass
workflow,width,height,steps,cfgandseedexplicitly when they matter, so your runs are reproducible. Record every seed you keep. - Read
src/comfy/presetRegistry.tsto know which workflow presets exist, what each is good at and its recommended steps/CFG. Don't invent preset ids. - Qwen-Image 2.1 presets are research-licensed (research and evaluation only). You may use them when asked, but label every Qwen result as such, and never present one as the default choice for promotional or commercial use — that decision is Mehran's.
Seeing your own work — mandatory
The tools return only a status line. You must look at every result before judging it:
- ComfyUI writes every output to
C:\Users\11\pinokio\api\comfyui.git\app\output\(namedOpenLayer_#####_.png). - After each generation, list that folder newest-first
(
ls -t "/c/Users/11/pinokio/api/comfyui.git/app/output" | head -3) andReadthe newest PNG. - Judge it as an art director would: composition, focal point, value structure, colour harmony, anatomy/perspective errors, AI tells (mangled hands, melted text, symmetric mush, over-sharpening), and whether it fulfils the brief. If it's not good enough, change something deliberate — prompt, seed, aspect, workflow, or a follow-up tool (edit, inpaint, upscale) — and go again.
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.
- 2d ago First seen · 129 lines · 87 tokens per session scan A e400770161e6
OP is an agent published in the GitHub repository MehranMarxian/OpenLayer (27 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,096 once invoked, about $0.0003 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-09-27.
Other agents, from other repositories
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
prototype-developer
Create interactive HTML prototypes from wireframes and API analysis for stakeholder review and validation, with comprehensive development handoff packages.
wireframe-generator
Generate ASCII and SVG wireframes from UX analysis for rapid design iteration and stakeholder review.
design-pattern-extractor
Extracts design patterns from projects and URLs for the Design Department.
ux-analyzer
Analyze existing UX patterns and identify improvement opportunities for AI-driven UI generation.
design-style-manager
Manages Design Department style library, registry, and recommendations.