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.
npx skills add Oriolshhh/runware-image-mcp --skill build-contextgit 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/skills/oriolshhh/runware-image-mcp/build-context)<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/build-context"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/build-context/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/skills/oriolshhh/runware-image-mcp/build-context"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/build-context.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.00016 | $0.01149 |
| Opus 5.5 | $0.00006 | $0.00460 |
| Sonnet 5.5 | $0.00003 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
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 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 — 124 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.
- 1mo ago First seen · 124 lines · 16 tokens per session scan A bd57bce31e42
build-context is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,149 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 skills, from other repositories
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.