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/hamchowderr/braynee/sessionsnpx skills add hamchowderr/braynee --skill sessionsgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00050 | $0.00462 |
| Opus 5 | $0.00025 | $0.00231 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade B, and why
sessions scanned grade B with 1 finding 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Your `~/.claude/settings.json` already has `session-export-qmd.js` and `session-auto-close.js` What it actually says
Sync Sessions Skill
Export Claude Code conversations to 2. Areas/Sessions/ as structured Obsidian notes.
Commands
# Sync current session
python3 {baseDir}/scripts/sessions.py sync
# Export today's sessions
python3 {baseDir}/scripts/sessions.py export --today
# Export all sessions
python3 {baseDir}/scripts/sessions.py export --all
# List active sessions
python3 {baseDir}/scripts/sessions.py list
# Resume a session (pick from list)
python3 {baseDir}/scripts/sessions.py resume --pick
# Add timestamped note to current session
python3 {baseDir}/scripts/sessions.py note "figured out the auth bug"
# Close session with summary
python3 {baseDir}/scripts/sessions.py close "scaffold complete, moving to next task"
Output Format
Sessions exported to 2. Areas/Sessions/ with frontmatter:
---
type: claude-session
date: YYYY-MM-DD
session_id: uuid
title: "..."
summary: "..."
messages: 42
status: active | done | blocked | handoff
tags: []
rating: null
comments: |
[2026-05-04 10:30] Note here
---
Preserved on Re-Sync
## My Notessectioncomments,tags,rating,statusfrontmatter fields
Auto-Sync Hook
Your ~/.claude/settings.json already has session-export-qmd.js and session-auto-close.js
on the Stop event — no additional hooks needed. Session export is already automated.
Use the export command manually when you want to bulk-sync historical sessions.
What ships with it
1 file 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.
- yesterday First seen · 71 lines · 50 tokens per session scan B e632a6957fe8
sessions is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 462 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.