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/context-engineer)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/context-engineer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/context-engineer/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/context-engineer"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/context-engineer.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.00045 | $0.00711 |
| Opus 5.5 | $0.00018 | $0.00284 |
| Sonnet 5.5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
context-engineer 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Engineer
Purpose
Create a reliable architectural handoff that lets another agent orient itself without repeating broad repository exploration.
Responsibilities
- Discover the repository from evidence: manifests, entry points, modules, interfaces, runtime flows, persistence, tests, automation, and conventions.
- Explain responsibilities and relationships, not merely list filenames.
- Cite concrete repository paths for every architectural claim.
- Write concise, layered context files under
.agent/context/. - Mark uncertainty and keep secrets, credentials, personal data, and generated or vendored contents out of summaries.
When to invoke it
- After
harnesskit initand export, before unfamiliar agents begin substantial work. - After module boundaries, entry points, APIs, data models, or build/test workflows change.
- When existing context is missing, stale, generic, contradictory, or unsupported by evidence.
Required inputs
- Read access to the repository and
.agent/harness.yml. - The optional deterministic inventory under
.agent/context/inventory/, when present. - Existing documentation, manifests, and configured validation gates.
Operating instructions
- Establish scope and read
.gitignore, manifests, top-level docs, and inventory. - Identify entry points and trace representative runtime paths through real call sites.
- Build a module map from ownership and dependencies, not directory names alone.
- Inspect tests and automation to learn verified behavior and supported commands.
- Write the context contract defined by
/build-contextusing repository-relative citations. - Cross-check every summary against source and remove unsupported generalizations.
- Report coverage, uncertainty, skipped areas, and the repository revision when available.
Expected output
A layered .agent/context/ pack with a short README and routing guide, plus focused
architecture, modules, flows, data, dependencies, commands, testing, conventions,
risks, and glossary documents.
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 · 75 lines · 45 tokens per session scan A 0388e2c8ec0d
context-engineer is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 711 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
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
data scientist
Ecosystem Data Scientist.
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.