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/rules/oriolshhh/runware-image-mcp/context-compression)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/context-compression"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/context-compression/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/rules/oriolshhh/runware-image-mcp/context-compression"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/context-compression.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.00009 | $0.00383 |
| Opus 5.5 | $0.00004 | $0.00153 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
context-compression 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.
What it actually says
Skill: context-compression
Context Compression
Purpose
Reduce large logs, transcripts, and outputs to a compact summary that preserves every fact needed to continue the work.
When to use it
- Long tool output, test logs, or build logs.
- Handing off context near a context-window limit.
Instructions
- Preserve exact failures, commands, filenames, line numbers, and assertions.
- Preserve API changes, decisions, and open risks verbatim.
- Summarize repetitive or noisy passages; never drop a unique fact.
- Separate observed facts, inferences, and uncertainty.
- State explicitly what was omitted and why.
Output format
- Facts (observed, exact).
- Inferences (clearly labeled).
- Open / uncertain.
- Omitted (what was dropped and why).
Anti-patterns
- Paraphrasing an error message and losing its exact text.
- Presenting an inference as an observed fact.
- "Compressing" by deleting information that is still needed.
Verification checklist
- A new reader can identify the objective, current state, exact failures, decisions, constraints, modified files, verification results, and next action.
- Repeated material is collapsed, while every unique fact remains.
- Sensitive values are omitted or redacted without hiding that redaction occurred.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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 · 46 lines · 9 tokens per session scan A 19278a81df51
context-compression is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 383 once invoked, about $0.0000 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-03.
Other cursor rules, from other repositories
knowledge
This file explains the Knowledge Base feature and how it's implemented.
tag-taxonomy-agent
This rule is essential when working with Obsidian vault knowledge management and need to maintain consistent tag taxonomy. Apply this rule when: (1) Normalizing and hierarchically organizing tag taxonomy across the vault, (2) Consolidating duplicate or similar tags (e.g., "ai-agents" and "ai/agents"), (3) Ensuring…
vault-performance-optimizer-agent
This rule is essential when working with Obsidian vault knowledge management and need to optimize performance and storage efficiency. Apply this rule when: (1) Analyzing vault performance including loading times and search performance, (2) Optimizing file sizes by identifying and addressing large files affecting…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.