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/postindustria-tech/agentic-toolkit/session-completionnpx skills add postindustria-tech/agentic-toolkit --skill session-completiongit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00105 | $0.01799 |
| Opus 5 | $0.00053 | $0.00899 |
| Sonnet 5 | $0.00021 | $0.00360 |
| Haiku 4.5 | $0.00011 | $0.00180 |
Grade A, and why
session-completion 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Completion Workflow
Overview
This skill is the final step in the development workflow managed by the beads plugin (/beads:workflow). Session completion is typically triggered after completing Step 4 (Verify & Close) in the beads workflow, ensuring all work is properly committed and pushed to remote.
Core Principle
Work is NOT complete until git push succeeds. This workflow ensures no work is lost between sessions or during conversation compaction.
Quick Checklist
Before ending any work session:
MANDATORY (always required):
- ✅ Run verification steps if code changed
- ✅ Push to remote repository
- ✅ Verify working tree is clean and synchronized
CONDITIONAL (task-dependent):
- ✅ Check incomplete work in issue tracking system
- ✅ File issues for remaining work
- ✅ Close completed tasks
CRITICAL: Never say "ready to push when you are" - YOU must complete the push.
Step-by-Step Workflow
Step 1: Check Incomplete Work
Review issue tracking system for in-progress tasks.
For each in-progress task:
- Can you finish it quickly? → Complete and close it
- Is it blocked? → Update status/description, leave in_progress
- Changed scope? → Close and create new issue for actual work
Don't leave tasks hanging without clear status.
Step 2: File Issues for Remaining Work
Create issues for:
- Follow-up tasks discovered during work
- Known limitations or technical debt
- Tasks that need requirements clarification
- Refactoring opportunities identified
Update project roadmap if priorities changed.
Step 3: Run Verification Steps
MANDATORY if code changed:
Run project-specific verification:
# Example verification commands
make quality # Run linters, type checkers, tests
npm test # JavaScript/TypeScript projects
pytest # Python projects
cargo test # Rust projects
If violations found:
- Auto-fix safe issues using linters
- Manually fix remaining violations
- For complex violations: create issues, then proceed
- Verify: All checks must pass before commit
What ships with it
8 files 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.
- 2d ago First seen · 311 lines · 105 tokens per session scan A 7c8b8d331255
session-completion is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 1,799 once invoked, about $0.0005 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.