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 RasputinKaiser/Self-Improvement-Plugin --skill sips-repo-mapgit clone --depth 1 https://github.com/RasputinKaiser/Self-Improvement-PluginWrote 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/rasputinkaiser/self-improvement-plugin/sips-repo-map)<a href="https://agentmods.dev/skills/rasputinkaiser/self-improvement-plugin/sips-repo-map"><img src="https://agentmods.dev/badge/skills/rasputinkaiser/self-improvement-plugin/sips-repo-map.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.1 | $0.00039 | $0.00143 |
| Opus 5 | $0.00019 | $0.00072 |
| Sonnet 5 | $0.00008 | $0.00029 |
| Haiku 4.5 | $0.00004 | $0.00014 |
Grade A, and why
sips-repo-map 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.
What it actually says
SIPS Repo Map
Use homebase_repo_map before touching unfamiliar repos or when the user asks for blast radius. Include any planned write set so the map can reason about scope.
Use the output to choose focused file reads and likely verification commands. Do not use broad recursive reads when rg --files, rg, and the repo map can narrow the target.
If the worktree is dirty, identify unrelated changes and leave them alone unless they directly affect the requested task.
What ships with it
3 files 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.
- 8d ago First seen · 13 lines · 39 tokens per session scan A 774ad93841a8
sips-repo-map is a skill published in the GitHub repository RasputinKaiser/Self-Improvement-Plugin (8 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 143 once invoked, about $0.0002 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-31.
Other skills, from other repositories
agi
Evidence-grounded autonomous engineering router. Use when the user invokes $agi or asks for broad, ambiguous, long-running, production-grade, benchmark-driven, or high-leverage software work that should choose its own tools, skills, agents, validation, and checkpoints from live repo evidence.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…