Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Filip-Podstavec/claude-leverage/plugin install claude-leverageWrote 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/filip-podstavec/claude-leverage/refresh-context-map)<a href="https://agentmods.dev/skills/filip-podstavec/claude-leverage/refresh-context-map"><img src="https://agentmods.dev/badge/skills/filip-podstavec/claude-leverage/refresh-context-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.00075 | $0.01126 |
| Opus 5 | $0.00037 | $0.00563 |
| Sonnet 5 | $0.00015 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
refresh-context-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 6d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
refresh-context-map
Rebuild the smart-context-surface manifest used by the PreToolUse hook
(scripts/hooks/context-surface.sh). See
docs/adr/0008-smart-context-surfacing-via-pretooluse-hook.md
for the design rationale.
When to invoke
- After adding / moving / deleting
AIDEV-NOTE/AIDEV-TODO/AIDEV-QUESTIONanchors. - After adding / removing per-directory
AGENTS.mdfiles. - After adding new ADRs in
docs/adr/that reference specific source files. - After a
git mergethat touched anchor-bearing files (.gitattributeskeeps the local manifest on conflict viamerge=ours, but it'll be stale relative to the merged tree until rebuilt). - When
/stack-checkflags drift between the manifest andgit ls-files. - Once per significant refactor that moved a lot of files.
When NOT to invoke
- On every commit — opt-in pre-commit hook (
.githooks/) does it automatically if enabled. If you've enabled it, manual/refresh-context-mapis redundant. - When you have not adopted the smart-context-surfacing stack in this repo
(no
.claude-leverage-context-map.jsonpresent means the PreToolUse hook silently no-ops — nothing to refresh).
What it does
Runs:
python ${CLAUDE_PLUGIN_ROOT}/scripts/build-context-map.py
from the repo root. The script:
- Walks every git-tracked file (via
git ls-files), skipping binaries (NUL-byte sniff). - For each file with
AIDEV-*anchors, indexes:- Anchors inside the file
- Anchors in sibling files (same directory)
- The chain of
AGENTS.mdfromdirname(file)to repo root - ADR files (
docs/adr/*.md) that mention this file path verbatim (word-boundary match)
- Writes
.claude-leverage-context-map.jsonat the repo root, atomically (.tmp+ rename).
The PreToolUse hook reads this manifest on every Read/Edit/Write/MultiEdit
and injects a per-file context slice via hookSpecificOutput.additionalContext.
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.
- 6d ago First seen · 105 lines · 75 tokens per session scan A 5f042d7ecde6
refresh-context-map is a skill published in the GitHub repository Filip-Podstavec/claude-leverage (68 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,126 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
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
resume
Load a previous session from TokenMizer graph memory. Returns a compact context block (100-600 tokens) covering goals, completed work, decisions, open tasks, and files. Inject this as system context to continue exactly where you left off. Use when user says "resume", "continue from last time", "load my project", "what…
checkpoint
Save the current session to TokenMizer graph memory. Creates a persistent checkpoint with all tasks, decisions, files, and errors — resumable in any future session. Use when user says "save", "checkpoint", "remember this", "I'm done for today", or session is getting long.
pickup
Resume work on this project after an interruption or at the start of a new session: show recent wins, what was being done, the next action, and open decisions, in that order, then stop. Trigger only on an explicit /squirrel:pickup invocation, or an explicit request to resume or pick up this project's past work at the…
stash
Record one durable memory in the user's cross-project hoard: a correction, a decision with its reasoning, a bug and its fix, or a fact worth keeping. Only for an explicit /squirrel:stash invocation.
claude-bridge-role-memory-keeper
Playbook for a Claude Code agent in the dedicated memory keeper role — single-writer for shared agent memory across a team of 3+ peers. Use when you are designated as the keeper (= other peers send you write candidates, you write them and watch for drift). Memory hygiene + reconciliation against the canon + drift…