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 skills add sxhmilyoyo/sundayhao-plugins --skill session-managergit clone --depth 1 https://github.com/sxhmilyoyo/sundayhao-pluginsWrote 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/sxhmilyoyo/sundayhao-plugins/session-manager)<a href="https://agentmods.dev/skills/sxhmilyoyo/sundayhao-plugins/session-manager"><img src="https://agentmods.dev/badge/skills/sxhmilyoyo/sundayhao-plugins/session-manager/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/skills/sxhmilyoyo/sundayhao-plugins/session-manager"><img src="https://agentmods.dev/badge/skills/sxhmilyoyo/sundayhao-plugins/session-manager.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.00132 | $0.01732 |
| Opus 5 | $0.00066 | $0.00866 |
| Sonnet 5 | $0.00026 | $0.00346 |
| Haiku 4.5 | $0.00013 | $0.00173 |
Grade A, and why
session-manager 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Manager
Manage metadata for the current active session's session.md file via Obsidian CLI.
Deriving the Session Path
The session docs path is injected into your system prompt by the SessionStart hook. It looks like:
Session docs path: {KB_PATH}/_sessions/2026-03-04/abc123-def456/docs/
To get the session.md vault-relative path for Obsidian CLI:
- Take the injected docs path
- Find
_sessions/in it — everything from_sessions/onward is vault-relative - Remove the trailing
docs/and appendsession.md
Example:
- Injected:
.../knowledge-bank/_sessions/2026-03-04/abc123-def456/docs/ - Vault-relative session.md:
_sessions/2026-03-04/abc123-def456/session.md
If the session docs path is not in your system prompt, ask the user for the session folder path.
Properties You Can Update
| Property | Type | Purpose |
|---|---|---|
session_name |
text | Session name (auto-synced from /rename customTitle on invocation) |
project |
text | Project name (auto-set from cwd at session start, customizable) |
tags |
list | Freeform categorization (e.g., brainstorming, debugging, architecture) |
summary |
text | One-line description of what the session accomplished |
Do NOT modify other frontmatter properties (session_id, date, cwd, etc.) — those are managed by hooks.
Commands
Set a property:
obsidian vault="knowledge-bank" property:set name="<property>" value="<value>" [type="list"] path="<vault-relative-path>"
Read current metadata:
obsidian vault="knowledge-bank" read path="<vault-relative-path>"
Tag Suggestion Workflow
When the user wants to set tags, do NOT set them directly. Instead, suggest existing tags to promote consistency.
Step 1: Load existing tags
Read from ccfind's cache (field 5, comma-separated):
CACHE="${XDG_CACHE_HOME:-$HOME/.cache}/ccfind/sessions.tsv"
cut -f5 "$CACHE" 2>/dev/null | tr ',' '\n' | sed 's/^ *//;s/ *$//' | grep -v '^-$' | grep -v '^$' | sort -u
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.
- 9d ago First seen · 161 lines · 132 tokens per session scan A ce9e2aaab25a
session-manager is a skill published in the GitHub repository sxhmilyoyo/sundayhao-plugins (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 132 tokens to every session and 1,732 once invoked, about $0.0007 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
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
pocket-init
Onboards an existing (brownfield) project onto Pocket. Scans the codebase and writes a project memory file (CLAUDE.md or AGENTS.md), optionally enables Pocket Enterprise (mode init) and scaffolds GitHub issue/PR templates. Trigger on "pocket-init", "set up pocket", "onboard this project", "generate CLAUDE.md", "enable…
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
memory-protocol
A shared set of rules for using a persistent memory service across coding-agent sessions.