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 agentmods add skills/ericwang915/pythonclaw/session_logsnpx skills add ericwang915/PythonClaw --skill session_logsgit clone --depth 1 https://github.com/ericwang915/PythonClawWhat 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 | $0.00055 | $0.00482 |
| Opus 5 | $0.00028 | $0.00241 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
session_logs 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.
What it actually says
Session Logs
Search your complete conversation history stored in session Markdown files.
When to Use
✅ USE this skill when:
- "What did we talk about yesterday?"
- "Find the conversation where I asked about X"
- "How many sessions have I had?"
- "What was the decision we made about Y?"
- User references a past conversation not in current context
When NOT to Use
❌ DON'T use this skill when:
- Current session context → already in your message history
- Application error logs → use
read_fileon log files directly - Non-PythonClaw logs → use
run_commandwith grep/rg
Session File Location
Session files are stored under ~/.pythonclaw/context/sessions/.
Each session is a Markdown file named <session_id>.md containing the full
conversation transcript.
Commands
List all sessions by date and size
ls -lhS ~/.pythonclaw/context/sessions/*.md
Search across ALL sessions for a keyword
python {skill_path}/search_sessions.py "keyword"
Or with grep:
grep -rl "keyword" ~/.pythonclaw/context/sessions/*.md
Read a specific session
cat ~/.pythonclaw/context/sessions/<session_id>.md
Count sessions
ls ~/.pythonclaw/context/sessions/*.md | wc -l
Notes
- Session files are append-only Markdown
- Large sessions can be several hundred KB — use
head/tailfor sampling - Session IDs follow the pattern
<channel>_<id>(e.g.telegram_123456,web_default) - The
history_detail.jsonlfile contains structured tool-call logs
Resources
| File | Description |
|---|---|
search_sessions.py |
Search across all session files by keyword |
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.
- 2d ago First seen · 81 lines · 55 tokens per session scan A 599d3cb35fc8
session_logs is a skill published in the GitHub repository ericwang915/PythonClaw (41 stars, last pushed 24d ago), licensed MIT. It adds 55 tokens to every session and 482 once invoked, about $0.0003 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
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
antfu
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
conventional-commits
Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases.
tencent-channel-community
腾讯频道(QQ频道)社区管理 skill（CLI 版）。频道创建/设置/搜索/加入/退出，成员管理/禁言/踢人，帖子发布/编辑/删除/移动/搜索，评论/回复/点赞，版块管理，分享链接解析，频道私信，加入设置管理，内容巡检，问答自动回复。涉及腾讯频道、频道帖子、频道成员相关任务时应优先使用。.
migrate-zhin-plugin-runtime
Migrate legacy Zhin.js plugins and projects to the convention-based Plugin Runtime — from usePlugin/getPlugin/addCommand/addMiddleware/addComponent/addTool/addCron/declareConfig/useContext and mutable registries to definePlugin + capability directories + Scope/Token resources. Use this whenever a Zhin plugin fails to…
zhin-audit
Audit Zhin.js monorepo for security vulnerabilities, performance bottlenecks, and architecture issues. Use when asked to "audit code", "check security", "find performance issues", "review architecture", "scan for vulnerabilities", "check memory leaks", or "review code quality".