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/summarize-subsystemsnpx skills add mimfort/rag_for_git --skill summarize-subsystemsgit 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/summarize-subsystems)<a href="https://agentmods.dev/skills/mimfort/rag_for_git/summarize-subsystems"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/summarize-subsystems.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.00089 | $0.02795 |
| Opus 5 | $0.00044 | $0.01398 |
| Sonnet 5 | $0.00018 | $0.00559 |
| Haiku 4.5 | $0.00009 | $0.00280 |
Grade A, and why
summarize-subsystems 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize subsystems (community summaries)
Cluster the base code graph into subsystems (by module path) and write a short, grounded
summary for each, persisted for ask / PR-walkthrough to use as a cheap high-level prior. This
skill reads code and writes summaries to the reviewer store; it does NOT modify code or post to
GitHub.
Always write summaries and answer the user in Russian (the project language), regardless of this
file's language. Tool calls, code identifiers and path:line stay verbatim.
Tools
Plus list_subsystem_clusters, get_subsystem_summary_work, get_file_skeletons,
index_subsystem_summary, prune_subsystem_summaries and backfill_summary_embeddings
(reviewer MCP). File-summary jobs read source ONLY through get_file_skeletons; the harness
Read is not used on source files in this skill.
Pipeline
- Resolve repo/branch.
-
List clusters (compact, paginated). Walk every page: call
list_subsystem_clusters(repo, branch, compact=True, limit=100), then repeat withoffset += 100while the response hashas_more == true. Stop only whenhas_more == false— a partial walk is not a full pass. Empty /noteabout an empty index → tell the user (in Russian) to runrag-reviewer:sync-codebasefirst, then stop.Every page carries the same whole-set fields:
depth(the applied cluster depth),layout_token(server-owned identity of the effective default depth plus sorted per-prefix overrides),depth_source(env|.review.yml|arg),deferred(stale clusters held back this pass under the cost cap, envSUMMARY_REBUILD_CAP),deferred_files(their pending file jobs),orphans(stored summaries whosecluster_keyis no longer a current cluster), andtotal_clusters(non-deferred clusters across the whole set, page-independent).The compact listing deliberately does not carry file-level data: each cluster gives
cluster_key,num_members,source_hash,stale,bootstrap,full_rebuild,reused_filesand the numeric countersadded,changed,removed,moved— no paths and no fingerprints. That keeps the listing O(clusters) instead of O(files). Per-cluster file detail comes fromget_subsystem_summary_workin step 5.
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 · 169 lines · 89 tokens per session scan A 9b0677672cbc
summarize-subsystems is a skill published in the GitHub repository mimfort/rag_for_git (21 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 2,795 once invoked, about $0.0004 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).