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/apappascs/claude-code-sessions/session-tasksnpx skills add apappascs/claude-code-sessions --skill session-tasksgit clone --depth 1 https://github.com/apappascs/claude-code-sessionsWhat 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.00061 | $0.00443 |
| Opus 5 | $0.00030 | $0.00221 |
| Sonnet 5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
session-tasks 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 Tasks
Aggregate tasks from the Tasks filesystem (~/.claude/tasks/) and session JSONL.
List all task lists
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts task-lists
All tasks across all task lists
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks
Filter by status
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --status pending
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --status in_progress
Tasks from a specific task list
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --task-list <task-list-id>
Fallback: tasks from a session JSONL (legacy)
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts tasks <session-jsonl-path>
Present results
Group tasks by status:
- In Progress tasks first (actively being worked on — check
activeFormfor current activity) - Pending tasks (need attention — check
blockedByfor dependencies) - Completed tasks
For each task show: subject, description, status, task list ID, dependencies.
If tasks have blocks/blockedBy relationships, show a dependency summary:
- "Task 2 (Add tests) is blocked by Task 1 (Setup project)"
Flag orphaned tasks — tasks with status "pending" or "in_progress" in task lists older than 7 days.
The source field indicates whether the task came from the filesystem ("filesystem") or was extracted from session JSONL ("jsonl").
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 · 60 lines · 61 tokens per session scan A e13af9a80511
session-tasks is a skill published in the GitHub repository apappascs/claude-code-sessions (4 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 443 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-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…