Session Archiver
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill matches its archiving purpose, but it silently persists chat transcripts and modifies startup behavior so background archiving can keep running.
Install only if you intentionally want automatic session archiving. Before using it, confirm where memory files are stored, whether sensitive chats should be excluded, how AGENTS.md will be changed, how cron/background runs are enabled, and how to disable or remove the archiver later.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Future sessions may keep launching archive work in the background without a visible reply or fresh approval.
The script edits AGENTS.md to add future startup instructions that spawn a background subagent, creating persistent autonomous behavior after the script runs.
const snippet = `5. **Session Auto-Archive** — Spawn background subagent to run `session-archiver` skill auto-archive script (archival + insights extraction, no reply needed)...`; fs.appendFileSync(AGENTS_MD, ...);
Require explicit user approval before editing AGENTS.md or enabling cron, document how to disable it, and provide a rollback command.
Private conversation content, accidental secrets, or adversarial instructions from a prior session could be retained and later influence the agent.
The script persists extracted user and assistant transcript text into daily memory files. It strips some metadata, but does not clearly quarantine instruction-like content or redact secrets.
return `${roleLabel} ${item.text}`; ... fs.appendFileSync(MEMORY_FILE, archiveContent + ...);Add explicit opt-in, sensitive-data redaction, clear exclusions, and a review/quarantine format for archived text before it becomes reusable memory.
Daily memory archive files older than 30 days may be removed without prompting.
The cleanup is scoped to dated .md files in the memory directory and is disclosed, but it still deletes user-visible archive files automatically.
if (mtime < cutoff) { fs.unlinkSync(filePath); cleaned++; }Make retention configurable and show users how to disable cleanup or recover from it.
It may be unclear to a user how the hourly background behavior is actually installed, audited, or disabled.
The artifacts describe hourly cron behavior in SKILL.md, but the install spec does not define a scheduler setup or removal path.
No install spec — this is an instruction-only skill.
Publish an explicit setup/removal spec for any cron integration and keep metadata aligned with the runtime behavior.