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/repository-mapping)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/repository-mapping"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/repository-mapping/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/repository-mapping"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/repository-mapping.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.00785 |
| Opus 5 | $0.00008 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
repository-mapping 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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: repository-mapping
Repository Mapping
Purpose
Turn repository evidence into a layered map that answers where work belongs, how the system behaves, and how changes are verified.
When to use it
- Building
/build-contextoutput for a new repository. - Refreshing context after architectural or workflow changes.
- Orienting before architecture, debugging, security, or cross-module work.
Instructions
- Scope: record repository root, revision when available, ignored/generated areas, monorepo boundaries, and unavailable systems.
- Discover: read manifests, root docs, configuration, entry points, package metadata, CI, migrations, and tests before drawing conclusions.
- Trace: follow representative user/request/job flows from entry point to side effects, including error paths and external boundaries.
- Map: group files into responsibility-based modules and record dependency direction, public interfaces, owners when known, and safe extension points.
- Verify: derive commands and behavior from checked-in scripts/configuration; run read-only discovery commands where safe and distinguish executed evidence.
- Write: produce layered summaries with paths, stable headings, cross-links,
a task-to-location routing table, and the required
/build-contextfrontmatter on every file. - Audit: remove generic statements, duplicated lists, secrets, stale paths, and claims that lack repository evidence.
Output format
context/README.md— scope, freshness, reading order, coverage, uncertainty.context/routing.md— task type → first files/modules/docs/tests/commands.context/architecture.md— system shape, boundaries, entry points, deployment.context/modules.md— responsibility, interfaces, dependencies, extension points.context/flows.md— important end-to-end runtime and failure flows.context/data.md— entities, schemas, persistence, migrations, ownership.context/dependencies.md— ecosystems, key dependencies, external services.context/commands.md— setup, run, lint, typecheck, test, build, release.context/testing.md— frameworks, layout, fixtures, coverage strategy.context/conventions.md— local patterns, naming, errors, configuration.context/risks.md— security/trust boundaries, hotspots, uncertainty, debt.context/glossary.md— repository-specific domain terms and acronyms.
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.
- 5d ago First seen · 70 lines · 16 tokens per session scan A 613eebb30b09
repository-mapping is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 785 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.