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/usefulmove/enso/read-session-logsnpx skills add usefulmove/enso --skill read-session-logsgit clone --depth 1 https://github.com/usefulmove/ensoWrote 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/usefulmove/enso/read-session-logs)<a href="https://agentmods.dev/skills/usefulmove/enso/read-session-logs"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/read-session-logs.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00044 | $0.00472 |
| Opus 5 | $0.00022 | $0.00236 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
read-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 3d 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
When to Use
Load this skill when:
- You need to review what happened in recent sessions
- You are joining an existing project and need session continuity
- A user asks to see "recent logs," "session history," or "what happened last time"
- Before starting work, you want to confirm the state left by the previous session
This is a read-only skill. No files are modified.
Workflow
Accept an optional argument: how many logs to show (default: 5).
Step 1: List Available Logs
ls -t docs/logs/*.md 2>/dev/null | head -${1:-5} || echo "(no session logs found in docs/logs/)"
Step 2: Display Each Log
ls -t docs/logs/*.md 2>/dev/null | head -${1:-5} | while read f; do
echo ""
echo "════════════════════════════════════════"
echo " $(basename $f)"
echo "════════════════════════════════════════"
cat "$f"
done || echo "No logs to display."
Do not summarize or paraphrase log content — show it as-is.
Step 3: Quick Reference Summary
Active stories:
ls docs/stories/*.md 2>/dev/null | while read f; do
echo "- $(basename $f): $(grep -A1 "^## Goal" "$f" 2>/dev/null | tail -1 | sed 's/^[[:space:]]*//')"
done || echo "(none)"
Recent key decisions (across shown logs):
ls -t docs/logs/*.md 2>/dev/null | head -${1:-5} | xargs grep -h "^- " 2>/dev/null | head -10 || echo "(none found)"
Display all of this clearly and concisely.
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.
- 3d ago First seen · 58 lines · 44 tokens per session scan A 79c5a09e7300
read-session-logs is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 472 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-31.
Other skills, from other repositories
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
pr-review
Review a GitHub pull request and post a verdict comment. Stateful — if a previous review comment exists, review only the new commits since the last review and track whether prior findings were addressed. Focus on code cleanliness, duplication, and docs sync. Use when user says "review this PR", "check the PR", "leave…
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.