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/commands/oriolshhh/runware-image-mcp/build-context)<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/build-context"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/build-context.svg" alt="Measured on agentmods" 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.01121 |
| Opus 5 | $0.00024 | $0.00561 |
| Sonnet 5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
build-context 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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-context — Build the repository knowledge pack
Purpose
Give future agents a concise, trustworthy starting point so they can locate relevant code and understand the system without repeating broad exploration.
Invocation
/build-context [optional scope, such as "backend" or "refresh changed areas"]
Accepted input
The repository, optional scope, existing .agent/context/, and optional inventory
from harnesskit context scan.
Prerequisites
- A HarnessKit workspace and permission to read the repository and write
.agent/context/. - No model API is called by the HarnessKit CLI; this command must run inside the consuming AI coding tool.
Procedure
- Read
.agent/harness.yml,.agent/README.md, root documentation, manifests,.gitignore, CI/configuration, and.agent/context/inventory/when present. - Inventory top-level systems and identify real entry points. Ignore generated, vendored, cache, binary, secret-looking, and oversized irrelevant files.
- Trace representative runtime flows through call sites: UI/request/CLI/job entry, domain logic, persistence/external effects, response/output, and failures.
- Map modules by responsibility. For each, record paths, public interfaces, incoming/outgoing dependencies, tests, and safe extension points.
- Derive setup/run/check/release commands from repository scripts and config. Label commands as verified only if actually run successfully.
- Describe data models, schemas, migrations, ownership, external services, trust boundaries, configuration, and operational risks when applicable.
- Write or refresh the twelve files defined by
repository-mapping. Preserve accurate existing material, remove stale claims, and use relative path citations. - Self-review: follow several routing entries back to source, check links/paths, scan for secrets, distinguish fact/inference/unknown, and compress repetition.
- Return a short coverage report: files written, important discoveries, verified commands, uncertain/skipped areas, and recommended refresh triggers.
- Keep
routing.mdconcise enough for coordinators to construct task-specific context capsules without loading the entire context pack.
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.
- 6d ago First seen · 125 lines · 49 tokens per session scan A 26590737fce3
build-context is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,121 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.