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 ph3on1x/wisci/plugin install wisciWrote 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/ph3on1x/wisci/compress)<a href="https://agentmods.dev/skills/ph3on1x/wisci/compress"><img src="https://agentmods.dev/badge/skills/ph3on1x/wisci/compress.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.00056 | $0.01245 |
| Opus 5 | $0.00028 | $0.00622 |
| Sonnet 5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
compress 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 5d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compress — Session Handoff Snapshots
Capture everything a fresh session needs to resume the current work. Each independent work stream gets its own file in .wisci/handoff/ — one writer per stream, so snapshots from different sessions never clobber each other. An index (.wisci/handoff.md) is regenerated by script, never written by hand.
Boundary: /compress stores work state (goal, progress, next steps). Reusable knowledge (research results, architecture notes, decisions worth keeping after the work ships) belongs in /write. If the session produced knowledge, tell the user to run /write <topic> — do not bury it in a handoff.
Current state
Timestamp: !date '+%Y-%m-%d %H:%M'
Existing handoff streams:
!python3 "${CLAUDE_PLUGIN_ROOT}/scripts/wisci.py" index --list
If the streams listing above shows an error or an unexpanded variable, run the bundled script manually: it is at scripts/wisci.py relative to this skill's directory. Run
python3 <that path> index --listwith Bash.
Execution Flow
-
Identify work streams. Review the session and list the independent streams of work it contains (usually one). A stream is work that would be resumed as a unit.
-
Match streams to leaves. Compare each session stream against the existing streams listed above (slug + goal):
- Clear match — this session continued that stream: update its leaf.
- No match — new leaf. Derive a slug from the stream's goal (kebab-case, lowercase, max 4 words). Never derive slugs from dates or branch names.
- Ambiguous match — create a new leaf. A fragmented stream is cheap to merge later; a wrongly merged one loses state. When creating due to ambiguity, mention the similar existing stream in your report.
- If
$ARGUMENTSnames a stream, use it verbatim as the slug and skip matching.
-
Write each leaf to
.wisci/handoff/<slug>.md(create directories as needed) using the leaf format below.- Union snapshot within the stream: capture the stream's full current state — including still-open items carried from the existing leaf — not just this session's delta.
- Never touch leaves for streams this session did not work on.
- A stream that finished: set
status: done. A stream waiting on something external:status: blockedand name the blocker.
What ships with it
1 file 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.
- 5d ago First seen · 94 lines · 56 tokens per session scan A ed1cdf444831
compress is a skill published in the GitHub repository ph3on1x/wisci (1 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 1,245 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
contorium-workspace-memory
Use Contorium workspace memory layers (focus, session events, Git, export) when resuming AI work or avoiding repeated project explanation.
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash.
context-compression
Design and evaluate compression strategies for long-running sessions.
context-optimization
Apply compaction, masking, and caching strategies.