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 zhaono1/agent-playbook --skill session-loggergit clone --depth 1 https://github.com/zhaono1/agent-playbookWrote 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/zhaono1/agent-playbook/session-logger)<a href="https://agentmods.dev/skills/zhaono1/agent-playbook/session-logger"><img src="https://agentmods.dev/badge/skills/zhaono1/agent-playbook/session-logger.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
- Snyk fail
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 82 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
- medium Rogue Agent · line 4 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00033 | $0.00602 |
| Opus 5 | $0.00016 | $0.00301 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
session-logger 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Logger
Create a compact recovery artifact without treating raw conversation history as durable memory.
Use This Skill When
- The user explicitly asks to save or record the current session.
- A supported host invokes the Agent Playbook
SessionEndhook with a transcript path. - A later task needs a concise handoff artifact and the user has authorized writing it.
Do not silently persist raw transcripts, credentials, private customer data, or unbounded agent output. Host support and write authority must be visible; skill metadata alone does not execute a hook.
CLI Runtime Contract
Claude Code installation can invoke:
agent-playbook session-log
The command reads the host-provided JSONL transcript and stores only bounded, redacted details:
- message counts;
- the last user prompt, truncated after redaction;
- up to 12 detected commands and file references;
- up to 8 detected questions;
- a hashed session reference and project identity.
By default, files are private local artifacts:
~/.agent-playbook/sessions/<project-id>/YYYY-MM-DD-<topic>.md
Set AGENT_PLAYBOOK_DATA_DIR or pass --data-dir to move the private data root.
Writing inside a repository is opt-in only:
apb session-log --session-dir ./sessions
If a repository-local directory is selected, verify its ignore and retention
policy before writing. Never assume another repository ignores sessions/.
Manual Summary Contract
When the host cannot provide a transcript event, create a user-authorized summary from the context actually visible in the current session. Include only:
- outcome and current state;
- decisions that affect future work;
- relevant files or commands;
- open questions and next proof gate.
State omissions honestly. Do not claim full conversation capture, structured decision extraction, automatic append behavior, or cross-session recall unless the active runtime demonstrably provides it.
Privacy and Safety
- Redact common credentials, bearer tokens, private keys, email addresses, and password/secret assignments before writing.
- Replace the current project root with a project identity in generated metadata.
- Write generated summaries with owner-only permissions where the platform supports it.
- Keep the artifact local unless the user separately authorizes commit, upload, or sharing.
- Treat redaction as risk reduction, not a guarantee that arbitrary confidential text is safe.
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.
- 7d ago First seen · 84 lines · 33 tokens per session scan A 3c9d4d9e0a06
session-logger is a skill published in the GitHub repository zhaono1/agent-playbook (77 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 602 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
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.
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.…
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…
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.
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…
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.