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/ryantlee25-droid/tages/session-contextnpx skills add ryantlee25-droid/tages --skill session-contextgit clone --depth 1 https://github.com/ryantlee25-droid/tagesWrote 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/ryantlee25-droid/tages/session-context)<a href="https://agentmods.dev/skills/ryantlee25-droid/tages/session-context"><img src="https://agentmods.dev/badge/skills/ryantlee25-droid/tages/session-context.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.00675 |
| Opus 5 | $0.00041 | $0.00338 |
| Sonnet 5 | $0.00016 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
session-context 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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Context — Restore Codebase Memory
Keywords
session start, project context, recall, what do you know about this project, load context, restore memory, previous session, remember, what did we learn, project conventions, codebase memory
Overview
Restore persistent codebase memory at the start of a session. Calls Tages MCP tools to hydrate the agent with conventions, architecture decisions, and project context from previous sessions. If Tages isn't configured for the current project, offers a smooth setup flow.
Use this skill when: Starting a new session, or when the user asks what you know about the project.
Workflow
Step 1: Hydrate Context
Call the brief tool to load a ranked, token-budgeted project context:
brief()
This returns the most important memories — gotchas, conventions, architecture decisions, and patterns — ranked by confidence, recency, and usage. High-value memories appear in full detail; lower-priority ones are summarized as compact key-value pairs. The token budget adapts to project size automatically.
Step 2: Handle the Result
Tool returns data (happy path):
Absorb the returned brief into your working context. Summarize briefly to the user:
Loaded project context — conventions, architecture decisions, and prior knowledge.
Do not dump the full memory contents unless asked. Use them silently to inform your work.
Tools error — Tages not configured (setup path):
If the tools fail because no Tages configuration exists for this project, offer setup:
Tages isn't configured for this project yet. I can set it up so I'll remember conventions, architecture decisions, and context across sessions.
- Cloud (recommended):
npx @tages/cli init— syncs to dashboard, works across machines- Local only:
npx @tages/cli init --local— SQLite only, no account neededWant me to set it up?
If the user says yes, run the appropriate init command. If no, proceed without memory and do not ask again 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.
- 5d ago First seen · 70 lines · 82 tokens per session scan A 3a55c5e12393
session-context is a skill published in the GitHub repository ryantlee25-droid/tages (4 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 675 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
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
kiro-steering-custom
Create custom steering documents for specialized project contexts.
honey-memory
Per-project persistent memory files indexed in MEMORY.md.