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 ericwang915/PythonClaw --skill session_logsgit clone --depth 1 https://github.com/ericwang915/PythonClawWrote 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/ericwang915/pythonclaw/session_logs)<a href="https://agentmods.dev/skills/ericwang915/pythonclaw/session_logs"><img src="https://agentmods.dev/badge/skills/ericwang915/pythonclaw/session_logs/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.
<a href="https://agentmods.dev/skills/ericwang915/pythonclaw/session_logs"><img src="https://agentmods.dev/badge/skills/ericwang915/pythonclaw/session_logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00482 |
| Opus 5.5 | $0.00022 | $0.00193 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 81 lines · 55 tokens per session scan A 599d3cb35fc8
session_logs is a skill published in the GitHub repository ericwang915/PythonClaw (45 stars, last pushed 10d ago), licensed MIT. It adds 55 tokens to every session and 482 once invoked, about $0.0002 per session on Opus 5.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
memory-consolidate
A memory-maintenance skill that stores a small number of durable, searchable facts and keeps the main memory file concise.
proactive-agent
Transform agents from task-followers into proactive partners.
knowledge-graph-memory
Full docs: read SKILL-REFERENCE.md.
self_awareness
Ground self-referential answers in the agent's actual filesystem. Use when the user asks who the agent is, what it can do, what it knows, what it remembers, what it has built, what services are connected, or what rules it follows.
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
consolidate-memory
Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.