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 agentmods add skills/mimfort/rag_for_git/pr-walkthroughnpx skills add mimfort/rag_for_git --skill pr-walkthroughgit clone --depth 1 https://github.com/mimfort/rag_for_gitWrote 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/mimfort/rag_for_git/pr-walkthrough)<a href="https://agentmods.dev/skills/mimfort/rag_for_git/pr-walkthrough"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/pr-walkthrough.svg" alt="Measured on agentmods" 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 | $0.00094 | $0.00824 |
| Opus 5 | $0.00047 | $0.00412 |
| Sonnet 5 | $0.00019 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
pr-walkthrough 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR walkthrough (reading guide for a human reviewer)
Help a human reviewer orient in a PR — not find bugs. Produce a markdown guide: where to start
(by centrality), what each file changes, and what it impacts ("careful, affects X"). Separate from
bug findings (review-pr).
Always answer the user in Russian (the project language). Tool calls, identifiers and path:line
stay verbatim.
Tools
Plus the PR-session tools (reviewer MCP): prepare_review, get_impact, get_changed_file_diff,
find_callers, get_related_symbols, read_file; optional get_subsystem_summaries (PRI-159);
optional post_pr_walkthrough (only on explicit user request).
Pipeline
-
Resolve repo & prepare the session. Resolve
repo(git remote). Callprepare_review(repo, pr). If it returns{"status": "skipped"}(branch not in REVIEW_BRANCHES), tell the user (in Russian) and stop. -
Reading order (centrality). Call
get_impact(repo, pr)→ changed symbols and their callers. Order "start here" by how much depends on each changed symbol (most central first). Graph down → fall back to ordering by file (fail-open). -
What each file changes. For each changed file,
get_changed_file_diff(repo, pr, path)→ one line describing what it changes. -
Impact ("careful, affects X"). For the central changed symbols,
find_callers/get_related_symbols→ who depends on them. Every "affects X" must be backed by a real caller. -
Subsystem prior (optional).
get_subsystem_summaries(repo, pr.base_ref, query="<PR title + changed file paths>")→ name the touched subsystem(s) in one line. Pass the PR's target branchpr.base_ref(from theprepare_reviewresponse), NOT the local git branch — subsystem summaries are indexed per target branch (base:<branch>). Empty / unavailable → skip (fail-open). -
Assemble the guide (Russian markdown):
- Начни отсюда — ordered list (most central first).
- По файлам — one line per changed file.
- Осторожно, влияет на — impacted symbols + their callers.
- (optional) Подсистемы — 1–2 lines from summaries.
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.
- 4d ago First seen · 64 lines · 94 tokens per session scan A 02e233650896
pr-walkthrough is a skill published in the GitHub repository mimfort/rag_for_git (21 stars, last pushed 3d ago), licensed MIT. It adds 94 tokens to every session and 824 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
graft
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
codebase-exploration
Explore and understand codebases using SocratiCode semantic search, dependency graphs, and context artifacts. Use when exploring code, understanding architecture, finding functions/types, analysing dependencies, searching database schemas or API specs, or when socraticode/codebasesearch tools are available. Activates…
codebase-management
Set up, index, and manage SocratiCode codebase indexing. Use when the user wants to index a project, check infrastructure health, start/stop file watching, configure context artifacts, troubleshoot indexing issues, manage the code graph, or any SocratiCode administrative task. Activates when the user mentions…
agentmap
Use for TypeScript/JavaScript codebase navigation — symbol lookup, blast radius, reuse checks, and repo orientation. Prefer agentmap before serial grep when exploring imports, exports, or where a symbol lives. Package is @raymondchins/agentmap (not the unrelated npm package agentmap).