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 MarcinHamiga/code-indexing-mcp --skill cross-repo-debugginggit clone --depth 1 https://github.com/MarcinHamiga/code-indexing-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/marcinhamiga/code-indexing-mcp/cross-repo-debugging)<a href="https://agentmods.dev/skills/marcinhamiga/code-indexing-mcp/cross-repo-debugging"><img src="https://agentmods.dev/badge/skills/marcinhamiga/code-indexing-mcp/cross-repo-debugging/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/marcinhamiga/code-indexing-mcp/cross-repo-debugging"><img src="https://agentmods.dev/badge/skills/marcinhamiga/code-indexing-mcp/cross-repo-debugging.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.00037 | $0.00749 |
| Opus 5.5 | $0.00015 | $0.00300 |
| Sonnet 5.5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
cross-repo-debugging 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 2mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Repo Debugging
Overview
Trace failures as evidence chains across explicit repository boundaries. Rankings, copied errors, and matching symbols are not root-cause proof.
Workflow
- Call
mcp__code-indexing-mcp__list_projects. Select only related projects by ID or unambiguous path; never substitutesearch_code(all_projects=true)for deliberate scope. - Write the expected chain, such as
producer -> contract -> consumer -> persistence. Treat each boundary as a first-divergence hypothesis. - Check
mcp__code-indexing-mcp__project_statuswhen freshness is uncertain. In manual mode, refresh stale indexes withmcp__code-indexing-mcp__index_projectbefore trusting missing results. - Call
mcp__code-indexing-mcp__search_across_projectswith explicit selectors. Query separately for stable identifiers, producer serialization, consumer validation, and contract versions, aliases, artifacts, or configuration. - If one repository dominates the global ranking, do not infer absence elsewhere. Filter by
paths,languages, orkinds, or search overlapping boundary pairs or smaller shards. - Pivot concepts into exact identifiers. Use project-scoped
mcp__code-indexing-mcp__find_symbolfor declarations and semantic search for usages;find_symboldoes not resolve call sites. - Call
mcp__code-indexing-mcp__file_outlinebeforemcp__code-indexing-mcp__get_chunk. Fetch only the producer, boundary contract/configuration, and consumer code needed to compare names, casing, fields, versions, routes/topics, status handling, defaults, and environment keys. - Record evidence as
project/path:line. Stop when it proves the first broken boundary and why it breaks, or when static analysis narrows the failure to one boundary and names the missing runtime evidence.
Use dynamic request and correlation IDs in logs or traces, not as primary source queries. When static code aligns, request the minimum payload, route/topic, deployment version, configuration, and outcome evidence for the narrowed boundary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 48 lines · 37 tokens per session scan A 3731f0ef933b
cross-repo-debugging is a skill published in the GitHub repository MarcinHamiga/code-indexing-mcp (0 stars, last pushed 25d ago), licensed MIT. It adds 37 tokens to every session and 749 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…