wrap — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited wrap (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are generating a graceful session closure. Your job: summarize what happened, capture decisions and learnings, commit outstanding work, and leave a clean trail for the next session.
Gather what happened this session from available sources:
git log --oneline --since="<session_start>" for commits during this sessiongit diff --name-only and git diff --cached --name-only for uncommitted workIf git history is unavailable, generate the summary from your in-session memory instead.
Before proceeding, check if this session was already wrapped:
>> Continuing wrap (prior wrap at {time}). New work will be appended. and only summarize work done SINCE the prior wrap.Using your full session context (not just file names), produce:
If you track time across clients or projects:
Client allocation: [project-a: 60%, project-b: 40%]
Correct? (Press Enter to confirm, or provide corrections)If you don't use multi-client tracking, skip this step.
Review the session for memory candidates -- observations that should persist across sessions. Only extract entries that qualify under at least one criterion:
For qualifying entries:
Write the session summary to a daily log file. Choose the format that fits your project:
Append to docs/daily-logs/sessions/YYYY-MM-DD-digests.jsonl:
{
"session_id": "<unique-id>",
"date": "YYYY-MM-DD",
"started_at": "<ISO timestamp>",
"ended_at": "<ISO timestamp>",
"duration_minutes": 45,
"end_reason": "graceful_wrap",
"accomplishments": ["Narrative accomplishment 1", "Narrative accomplishment 2"],
"decisions": ["Decision and rationale"],
"learnings": ["Learning 1"],
"blockers": [],
"files_changed": ["path/to/file1.py", "path/to/file2.md"],
"commits": [{"hash": "abc1234", "message": "commit message"}]
}Always use append mode (open('a')) -- never read-all-write-all, as parallel sessions may write to this file concurrently.
Append to docs/daily-logs/sessions/YYYY-MM-DD.md:
---
_Session wrapped: TIMESTAMP (duration: Xh Ym)_
**Accomplishments:**
- Narrative accomplishment 1
- Narrative accomplishment 2
**Decisions:**
- Decision + rationale
**Learnings:**
- Learning
**Files changed:** N files
**Commits:**
- hash: messageYou can use both formats (JSONL for programmatic access, markdown for human scanning).
Commit this session's outstanding work automatically. This step runs AFTER digest writing so that digest files are included.
git status to see what's uncommitted.Auto-commit is the default. Do not ask for confirmation unless sensitive files are detected.
Print the final summary:
>> Session wrapped
Duration: Xh Ym
Accomplishments:
- accomplishment 1
- accomplishment 2
Decisions: N
Learnings: N
Commits: N (this session)
Files changed: N
Log: docs/daily-logs/sessions/YYYY-MM-DD.md[OK], [!], >> for indicators.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.