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/satsilem/ai-workflow-framework/start-sessionnpx skills add satsilem/ai-workflow-framework --skill start-sessiongit clone --depth 1 https://github.com/satsilem/ai-workflow-frameworkWrote 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/satsilem/ai-workflow-framework/start-session)<a href="https://agentmods.dev/skills/satsilem/ai-workflow-framework/start-session"><img src="https://agentmods.dev/badge/skills/satsilem/ai-workflow-framework/start-session.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.00082 | $0.00955 |
| Opus 5 | $0.00041 | $0.00477 |
| Sonnet 5 | $0.00016 | $0.00191 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
start-session 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Session
The goal is to orient quickly — give enough context to work effectively without overwhelming with detail. Think of it as a smart handoff from the last session.
Step 1 — Check files exist
Look for these files in the current working directory:
CLAUDE.mdSESSION.mdTODO.md.reference/INDEX.md(optional but recommended)
If any are missing, warn immediately:
⚠️ Missing: SESSION.md — no session history available
⚠️ Missing: TODO.md — no task list found
If CLAUDE.md is missing, note that the project may not be set up yet and
suggest running the project-setup skill.
Step 2 — Read the files strategically
- CLAUDE.md — read in full (it's the master reference, usually concise)
- .reference/INDEX.md — if present, read in full; this is the evergreen lookup map
- TODO.md — read strategically:
## Open Tasks— read in full (this is the canonical active work list)## Done— skip by default unless needed for clarification
- SESSION.md — read selectively:
- KEY LEARNINGS section — read in full (critical gotchas, always relevant)
- CHRONOLOGICAL LOG — read only the last 2-3 entries (recent = relevant)
- Skip everything older — it's history, not context
SESSION.md can be hundreds of lines. Don't read it all — the gotchas and recent entries are what matter for orienting quickly.
Use .reference/ for stable operational/docs lookup context. Use .ai-notes/ only when a specific investigation timeline is needed.
Step 3 — Produce the session brief
Use this structure. Keep each section tight — no padding, no repetition.
## Session Ready — [Project Name]
**Project:** [What this project is + current status in 2-3 lines]
**Last session:** [What was done + any key decisions made — 2-3 lines]
**Key gotchas:**
- [Top 2-3 warnings from KEY LEARNINGS most relevant right now]
- [Only include ones that could actually affect today's work]
**Open tasks:**
1. [!] [Important task title]
scope: ... | target: ... | owner: ... | next: ... | updated: YYYY-MM-DD
2. [!] [Next urgent task title]
scope: ... | target: ... | owner: ... | next: ... | updated: YYYY-MM-DD
3. [ ] [Remaining open task title]
scope: ... | target: ... | owner: ... | next: ... | updated: YYYY-MM-DD
**Suggested focus today:**
- [2-3 specific items Claude thinks deserve attention, based on context,
recency, and what was left unfinished last session]
**Reference docs to use:**
- [0-3 relevant files from `.reference/INDEX.md` for likely lookup during this session]
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.
- 4d ago First seen · 96 lines · 82 tokens per session scan A 9bd78280ba0d
start-session is a skill published in the GitHub repository satsilem/ai-workflow-framework (2 stars, last pushed 5mo ago), licensed MIT. It adds 82 tokens to every session and 955 once invoked, about $0.0004 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…