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/davidcpage/skill-issues/sessionsnpx skills add davidcpage/skill-issues --skill sessionsgit clone --depth 1 https://github.com/davidcpage/skill-issuesWhat 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.00034 | $0.01752 |
| Opus 5 | $0.00017 | $0.00876 |
| Sonnet 5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
sessions 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sessions Skill
Personal session memory for AI agent conversations. Captures learnings, open questions, and next actions across sessions.
Installation required: Install the skill-issues package for CLI tools:
uv tool install skill-issues
Dependency: This skill optionally references the issues skill via the issues_worked field. The dependency is one-way: sessions can reference issues, but issues never reference sessions.
Data Location
Sessions are stored in .sessions/events-{prefix}.jsonl (project root) - one JSON object per line, append-only. Each user writes to their own file (e.g., events-dp.jsonl), enabling conflict-free multi-user git workflows. Reading aggregates from all user files.
User Prefix
Session IDs include a user prefix (e.g., dp-s001) to enable multi-user collaboration. The prefix is resolved in order:
SKILL_ISSUES_PREFIXenvironment variablegit config skill-issues.prefix- Derived from
git config user.name(first + last initials) - Fallback:
xx
Configure once per machine:
git config --global skill-issues.prefix "dp"
On first use with a derived prefix, you'll see a hint about configuration.
Note: Sessions are filtered by user by default. Use --user all to see all users' sessions.
Quick Reference
# Reading (filtered to current user by default)
sessions # Last session (current user)
sessions --last 3 # Last N sessions (current user)
sessions --last 5 --user all # Last 5 from all users
sessions --user xy # Last session from user 'xy'
sessions --all # All sessions (current user)
sessions --open-questions # All open questions across sessions
sessions --next-actions # All next actions (with session attribution)
sessions --by-topic beads # Filter by topic
sessions --by-issue dp-014 # Filter: sessions that worked on a specific issue
sessions --summary # Markdown summary for documentation
sessions --timeline # Markdown timeline of sessions
# Writing
sessions --create "topic" [options]
# TUI
sessions board # Interactive session browser (with user tabs)
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 · 236 lines · 34 tokens per session scan A 9a79dabc910a
sessions is a skill published in the GitHub repository davidcpage/skill-issues (2 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 1,752 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…