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 naimkatiman/continuous-improvement --skill strategic-compactgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/strategic-compact)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/strategic-compact"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/strategic-compact.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.00051 | $0.00920 |
| Opus 5 | $0.00026 | $0.00460 |
| Sonnet 5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
strategic-compact 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Compact Skill
Suggests manual /compact at strategic points in your workflow rather than relying on arbitrary auto-compaction.
When to Activate
- Running long sessions that approach context limits (200K+ tokens)
- Working on multi-phase tasks (research → plan → implement → test)
- Switching between unrelated tasks within the same session
- After completing a major milestone and starting new work
- When responses slow down or become less coherent (context pressure)
Why Strategic Compaction?
Auto-compaction triggers at arbitrary points:
- Often mid-task, losing important context
- No awareness of logical task boundaries
- Can interrupt complex multi-step operations
Strategic compaction at logical boundaries:
- After exploration, before execution — Compact research context, keep implementation plan
- After completing a milestone — Fresh start for next phase
- Before major context shifts — Clear exploration context before different task
How It Works
This skill is a manual phase-boundary checklist, not a bundled runtime hook. Use it when planning or reviewing a long session:
- Name the current phase — research, planning, implementation, testing, debugging, release, or handoff.
- Check the next transition — decide whether the next phase needs fresh context or the current context is still load-bearing.
- Preserve state first — write the plan, todo list, findings, or handoff note that must survive compaction.
- Compact only at a boundary — if compaction helps, run
/compactwith a specific summary for the next phase. - Resume from durable artifacts — after compaction, re-read the plan/files instead of relying on lost conversation context.
Runtime Boundary
The current plugin does not ship strategic-compact PreToolUse automation or a threshold script. Treat compaction as an operator/agent decision: this skill gives the decision guide, while Claude Code's native /compact command performs the actual compaction.
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 · 86 lines · 51 tokens per session scan A 4c939a8644ca
strategic-compact is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 920 once invoked, about $0.0003 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
dreamd
Works with: Claude Code, Cursor, Cline, OpenCode, Codex CLI, Gemini CLI, Copilot agent mode, Roo Code, Goose — any MCP-aware harness.
context-efficient-coding
Use ContextFlux to minimize coding-agent context and tool calls when exploring, planning, debugging, reviewing, or modifying an unfamiliar or multi-file repository. Trigger for codebase discovery, symbol search, architecture questions, cross-file changes, error tracing, review feedback, test discovery, or any request…
remember
A memory-saving skill that stores facts, preferences, decisions, tasks, and other context in Super Memory, a local semantic memory store.
recall
A memory-search skill for finding previously saved information in Super Memory, a semantic memory store.
neurox
Persistent memory for AI agents — remember preferences, decisions, failures, and learnings across sessions.
peek
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if a decision was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.