session-log

session-log is a skill for Claude Code from michalparkola/tapestry-skills. It costs 48 tokens per session (1,146 once invoked), scanned A, original, MIT.

A tool for summarizing the current conversation and adding the results to a weekly agent log. The log is a dated record of work done by the coding agent.

In plain words
What is it for?
Use it when you want to record a session, add a plan or summary to the week's notes, or preserve a reusable result for later work.
Why use it?
It keeps useful decisions, findings, and reusable outputs in one ongoing file instead of leaving them only in chat history.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when you want to record a session, add a plan or summary to the week's notes, or preserve a reusable result for later work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michalparkola/tapestry-skills/session-log
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.

Any agent
npx skills add michalparkola/tapestry-skills --skill session-log
Clone the repo
git clone --depth 1 https://github.com/michalparkola/tapestry-skills

Made for: Claude Code.

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

agentmods badge for session-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/michalparkola/tapestry-skills/session-log/github.svg)](https://agentmods.dev/skills/michalparkola/tapestry-skills/session-log)
Your own site
<a href="https://agentmods.dev/skills/michalparkola/tapestry-skills/session-log"><img src="https://agentmods.dev/badge/skills/michalparkola/tapestry-skills/session-log/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.

agentmods 80×15 button for session-log

Your own site · 80×15
<a href="https://agentmods.dev/skills/michalparkola/tapestry-skills/session-log"><img src="https://agentmods.dev/badge/skills/michalparkola/tapestry-skills/session-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,146 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00048 $0.01146
Opus 5 $0.00024 $0.00573
Sonnet 5 $0.00010 $0.00229
Haiku 4.5 $0.00005 $0.00115

Measured 11d ago against content hash 75bb16fb56c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

session-log 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.

session-log/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Session Log

Summarize the current conversation and append to the weekly agent-log file.

Output Location

YYYY-wWW Agent Log.md

Where YYYY-wWW is the ISO week of today's date. Calculate with:

date +%Y-w%V

Format Rules

  1. Reverse chronological order — newest day on top
  2. One ## heading per day — format: ## YYYY-MM-DD
  3. Bullets, not subheadings — inside a day, use plain bullet - Topic title as topic separator, not ###. No bold, no formatting on topic lines.
  4. Details as nested bullets — one sentence per sub-bullet, can nest if needed for details. No bold. Nesting uses a TAB.
  5. CHUNK markers — if a topic produced a reusable output (a plan, a summary, a framework, a draft message), add nested bullet: CHUNK: <descriptive title>
  6. No explanatory text — no intros, no "in this session we discussed", no meta-commentary
  7. Append, don't replace — when a day heading already exists, add new bullets under it without removing existing content

Example

## 2026-02-28

- Analiza strategii X vs framework Y + moje obserwacje
  - Strategia jest silna w A i B, słaba w C — brakuje fosy i horyzontu 3+lat.
  - Naming produktu "Rescue" implikuje że kupujący jest ofiarą, co blokuje referencje.
  - Anty-segment nie jest sprawdzalny z zewnątrz — to opis doświadczenia, nie filtr.
  - CHUNK: 3-zdaniowe podsumowanie strategii
  - CHUNK: Scorecard po 6 osiach
- Decyzja: follow-up z klientem
  - Nie wysyłać feedbacku (nie prosił), wysłać link do artykułu jako wartość bez CTA.

Step-by-Step Workflow

1. Determine the target file

WEEK=$(date +%Y-w%V)

Target: ${WEEK} agent-log.md

2. Read existing file (if any)

The file may already have entries from earlier sessions this week. Read it first to avoid overwriting.

3. Review the full conversation and determine dates

Scan the entire conversation history. Identify:

  • Topics — distinct subjects discussed (group related back-and-forth into one topic)
  • Decisions — what was decided or concluded
  • Outputs — any reusable artifacts (summaries, plans, draft messages, frameworks, scorecards)

Read the full file on GitHub · 104 lines

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. 11d ago First seen · 104 lines · 48 tokens per session scan A 75bb16fb56c3

Subscribe to this mod's changes

session-log is a skill published in the GitHub repository michalparkola/tapestry-skills (540 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 1,146 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.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens