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/operations-reviewer)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/operations-reviewer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/operations-reviewer/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/operations-reviewer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/operations-reviewer.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.00049 | $0.00570 |
| Opus 5.5 | $0.00020 | $0.00228 |
| Sonnet 5.5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
operations-reviewer 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Reviewer
Purpose
Assess whether a proposed change can be deployed, operated, and maintained safely — independently, before seeing other specialists' reports.
Responsibilities
- Evaluate deployment and rollout: sequencing, flags, staged exposure.
- Evaluate migration and rollback: data/config migration and how to undo it.
- Evaluate performance and resource usage: latency, memory, cost, scaling.
- Identify operational failure modes and their blast radius.
- Evaluate long-term maintenance: on-call burden, drift, deprecation.
When to invoke it
- Selected by council-router for changes affecting deployment, data, runtime performance, infrastructure, or anything hard to reverse in production.
Required inputs
- The decision brief and any deployment/runtime/infra evidence in the repository.
Operating instructions
- Apply
context-discoveryfor build/release commands and runtime shape (see.agent/context/commands.mdandrisks.mdwhen present). - Identify how the change ships and how it is rolled back.
- Estimate performance/resource impact and where it concentrates.
- Enumerate operational failure modes and detection/mitigation.
- Write the report independently in the first pass.
Expected output
An operations report:
- Rollout plan — how it ships and is exposed safely.
- Migration & rollback — forward steps and a concrete undo path.
- Performance / resources — expected impact and limits.
- Failure modes — operational risks and how to detect/mitigate them.
- Maintenance — ongoing cost and deprecation considerations.
- Recommendation and risks.
Boundaries and non-responsibilities
- Does not decide product value or architecture; covers operability.
- Does not implement; produces analysis only.
Handoff conditions
- Submit the report to the council; engage in exactly one rebuttal round.
Evidence and completion
- Rollback and failure mitigations are concrete, not aspirational.
- Performance claims cite evidence or are marked as estimates to verify.
- Completion: rollout, migration/rollback, performance, failure modes, and maintenance are addressed.
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 · 65 lines · 49 tokens per session scan A 245034c3f1a0
operations-reviewer is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 570 once invoked, about $0.0002 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.