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 repository-mappinggit 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/repository-mapping)<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/repository-mapping"><img src="https://agentmods.dev/badge/skills/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/skills/oriolshhh/runware-image-mcp/repository-mapping"><img src="https://agentmods.dev/badge/skills/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.00020 | $0.00776 |
| Opus 5 | $0.00010 | $0.00388 |
| Sonnet 5 | $0.00004 | $0.00155 |
| 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 8d ago First seen · 67 lines · 20 tokens per session scan A c3681d672f46
repository-mapping is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 776 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 skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…