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 Omar-Obando/qwen-orchestrator --skill compaction-recoverygit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/compaction-recovery)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/compaction-recovery"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/compaction-recovery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/compaction-recovery"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/compaction-recovery.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01679 |
| Opus 5 | $0.00018 | $0.00839 |
| Sonnet 5 | $0.00007 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
compaction-recovery 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 11d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compaction Recovery Skill — Context Preservation Protocol
This skill ensures that when the LLM context window is compacted (compressed), no mission-critical information is lost. It defines what to preserve and how to restore it.
The Compaction Problem
When context is compacted:
- Previous conversation is summarized/compressed
- Detailed TODO items may lose their sub-task descriptions
- Implementation progress may be forgotten
- File-level assignment details may vanish
- Partial code changes may lose their context
Prevention Protocol
Write Everything Important to Files
NEVER rely on conversation context for critical information. ALWAYS persist to the active session directory.
Each /orchestrator invocation creates a new isolated session. The active session ID is stored in .qwen-orchestrator/current-session. All state writes go to .qwen-orchestrator/sessions/<session-id>/.
.qwen-orchestrator/
├── current-session # Active session ID (single line: YYYY-MM-DDTHH-MM-SS)
├── sessions/
│ ├── 2026-05-07T14-30-00/ # Archived session (IMMUTABLE — never modify)
│ │ ├── context.md
│ │ ├── memory.md
│ │ └── ...
│ └── 2026-05-07T16-45-00/ # Active session (pointed to by current-session)
│ ├── context.md # Project context (<150 lines)
│ ├── memory.md # Session state for recovery
│ ├── redesign-analysis.md # Redesign analysis (if applicable)
│ ├── tech-decisions.md # Technology decisions
│ ├── seo-report.md # SEO audit results
│ ├── sync-issues.md # Cross-file sync issues
│ ├── project-status.md # Progress tracking
│ ├── qa-report.md # Quality reports
│ ├── agent-health.md # Agent status tracking
│ ├── progress/
│ │ ├── mission-state.md # Current mission snapshot
│ │ ├── active-files.md # Files being worked on + status
│ │ └── decisions.md # Architecture decisions made
│ ├── checkpoints/
│ │ └── cp-[timestamp].md # Periodic checkpoint snapshots
│ └── docs/ # Cached documentation
│ └── *.md
└── shared/ # Cross-session persistent data (future use)
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.
- 11d ago First seen · 212 lines · 37 tokens per session scan A 30fea8ede9b2
compaction-recovery is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,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
loopx-material
Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate/archive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off…
loopx-doc-registry
Use when a connected LoopX project is asked to read, remember, record, index, register, or use a durable project material such as a Lark/wiki/design doc, research note, SOP, owner packet, migration report, benchmark paper, or external material source. Use even when the user does not mention LoopX or doc registry.
self_reflection
Periodically review memory for contradictions, gaps, stale information, and controlled improvement proposals.
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
brain_dump
Capture unstructured thoughts and organize them into structured notes saved to memory.
wiki_guide
Guidance for the Obsidian-compatible wiki vault.