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/koroqe/claude-code-sdlc/context-refreshnpx skills add Koroqe/claude-code-sdlc --skill context-refreshgit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWhat 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.00033 | $0.00679 |
| Opus 5 | $0.00016 | $0.00340 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
context-refresh 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: Context Refresh
Rebuild context from scratchpad to maintain clarity during long sessions.
Arguments
$mode (also available as $ARGUMENTS) optionally requests a specific mode. Literal-token flag rule: a documented flag is active ONLY if its literal token appears in $ARGUMENTS. Never infer that a flag was passed because the documentation describes it.
Process
1. Read Scratchpad
Read .claude/scratchpad.md and extract:
- Feature name and branch (
## Feature:,## Branch:) - Current status (
## Status:— idle/bootstrapping/implementing wave W slice N/M/implementing slice N/M/quality-gates/complete/blocked) - Plan progress by wave (if
### Wave Nsubheadings exist): which waves are complete, which wave is current, per-slice status within the current wave. If no wave subheadings, extract flat slice progress as before - Any blockers (
## Blockers) - Recent work from
## Completedsection
2. Verify Accuracy
Check if scratchpad matches current state:
- Are goals still accurate?
- Have new decisions been made?
- Are next steps still relevant?
- Has the git branch changed?
3. Update if Needed
If scratchpad is stale:
- Update current goal
- Add new constraints or decisions
- Log recent commits and changes
- Revise next steps based on progress
If scratchpad exceeds 100 lines:
- Move completed waves (all slices DONE) from
## Planto## Archiveas a unit — keep the### Wave Nblock together. If no wave subheadings, move completed slices individually - Keep only the current wave and next wave in
## Plan - Keep only the last 3 entries in
## Completed - This prevents the scratchpad itself from consuming excessive context
4. Summarize Context
Provide concise summary of where we are.
5. Recommend Action
Based on context health:
- Clean: Continue with current work
- Noisy: Suggest which details can be archived
- Stale: Update scratchpad with current state
- Overwhelming: Consider starting a fresh session with
claude -c
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.
- 2d ago First seen · 75 lines · 33 tokens per session scan A f7d191113f2a
context-refresh is a skill published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 679 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.