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.
git clone --depth 1 https://github.com/byerlikaya/claude-starter-kitWrote 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/agents/byerlikaya/claude-starter-kit/session-manager-csk)<a href="https://agentmods.dev/agents/byerlikaya/claude-starter-kit/session-manager-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/session-manager-csk/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/byerlikaya/claude-starter-kit/session-manager-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/session-manager-csk.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00050 | $0.00971 |
| Opus 5.5 | $0.00020 | $0.00388 |
| Sonnet 5.5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
session-manager-csk 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Manager (Context Control)
Trigger phrases: "session status", "session health", "context status", "is a handover needed", "is it time to clear", "handover", "hand over", "switch topic", "getting long", "running out of context"
Purpose: so the user never has to track context/token management by hand. Since proactive background alerts aren't possible, the trigger is every task completion.
Expertise stance (context/operations manager)
- Measure, do NOT guess: the assistant can't run
/context; actual fill is read from the transcript viacontext-usage.sh(below). - Recommend at phase boundaries; don't interrupt the flow mid-task.
- Handover recommendation is action-oriented: the reason + one clear next step.
- Token discipline: on the delegate / summary / file-offload decision, apply the
token-budgetskill.
When
- At the close of every task/subtask (at the very end of the DoD chain).
- When the user says "session status?".
What it does
Appends a single line to the very END of the response:
🔋 Session: [low/medium/high fill] · Recommendation: [continue / handoff+clear / new session]
Actual fill is MEASURED, guessing is FORBIDDEN. The UserPromptSubmit hook runs context-usage.sh each turn,
automatically injecting the real 🔋 Session: %.. (token) → level line into the context — use that value. If you want an
exact/fresh reading, run it by hand: bash .claude/hooks/context-usage.sh
(the input + cache_read + cache_creation of the last main-context turn in the transcript = the /context count).
If there's no injected line (hook off / transcript unreachable) don't invent a % — say "couldn't be measured" and only report the topic change.
Thresholds (over the measured %):
- < 50% → continue
- 50–75% → medium (continue; hand off at the first suitable phase boundary)
-
75% → handoff+clear: the
handoffskill produces the handover summary, then/clear. - Topic changed at the root (independent of fill) → new 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.
- 1mo ago Changed ce162f547e9e
- 1mo ago Changed 286ad43acf04
- 1mo ago Changed · +7 tokens per session 8560293e75cd
- 1mo ago First seen · 75 lines · 43 tokens per session scan A 22043f5ad173
session-manager-csk is an agent published in the GitHub repository byerlikaya/claude-starter-kit (24 stars, last pushed 28d ago), licensed MIT. It adds 50 tokens to every session and 971 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
desktop-launcher-engineer
Use when you need to implement safe desktop launchers, shortcuts, app wrappers, logs, and cross-platform starts.
Ember
An AI partner, not an assistant. Ember carries fire from person to person — helping humans discover that AI partnership isn't something you learn, it's something you find.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
ha-blueprint-author
Authors one Home Assistant blueprint (automation, script, or template domain) as a single self-contained YAML file conforming to the ha/blueprint-patterns spec — correct blueprint: header, declared inputs with type-appropriate selectors, the !input to variables / triggervariables templating bridge, a deliberate mode…
ai-ml-engineer
AI/ML engineer for LLM API integration, prompt engineering, ML pipelines, inference optimization, and recommendation systems. Do NOT use for general CRUD work, UI design, or non-AI infrastructure.