dearchive

A command that restores matching memories from Gnosys's archive back into the active store used for normal searches.

In plain words
What is it for?
Use it with a search phrase to find archived memories and restore them, optionally setting the maximum number to recover.
Why use it?
Archived memories are no longer in the active store, so ordinary searches may not find them. This command brings selected matches back when you need them again.

Command

Install

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.

agentmods
npx agentmods add commands/proticom/gnosys/dearchive
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00413
Opus 5 $0.00000 $0.00206
Sonnet 5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00041

Measured 2d ago against content hash f75a1daa7181, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dearchive 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.

docs/commands/dearchive.md · 73 lines

What it actually says

gnosys dearchive

Force-dearchive memories matching a query from archive.db back to the active store.

Usage

gnosys dearchive "auth decision"
gnosys dearchive "auth decision" --limit 10

Options

Option Description
--limit <n> Maximum archived memories to restore (default 5)

Behavior

  1. Resolves configured stores via the project resolver.
  2. Requires a writable store (getWriteTarget()).
  3. Opens GnosysArchive on the write-target path.
  4. Searches archived memories with searchArchive(query, limit).
  5. Restores matches with dearchiveBatch(ids, writeTarget.store).

Output

No matches:

No archived memories found matching "auth decision".

Matches found:

Found 2 archived memories matching "auth decision":

  • Auth Token Policy (deci-012)
  ...

Dearchived 2 memories back to active:
  → project/decisions/auth-token-policy.md

Errors

Condition Message
No stores No Gnosys stores found. Run gnosys init first.
No writable store No writable store found.
Archive unavailable Archive not available. Install it with: npm install better-sqlite3

Error paths exit with code 1.

Resource cleanup

Always closes the archive handle in a finally block, including when search or restore fails.

Validation

cd gnosys-public
npm run cli -- dearchive --help
npx vitest run src/test/dearchive-command-handler.test.ts
  • gnosys maintain — vault maintenance including archival workflows.
  • gnosys search — search active memories.
  • gnosys read — read a restored memory after dearchive.
Changes

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.

  1. 2d ago First seen · 73 lines · 0 tokens per session scan A f75a1daa7181

Subscribe to this mod's changes

dearchive is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 413 tokens. 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.