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/taizen-ai/taizen-claude-plugins/session-contextnpx skills add taizen-ai/taizen-claude-plugins --skill session-contextgit clone --depth 1 https://github.com/taizen-ai/taizen-claude-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/taizen-ai/taizen-claude-plugins/session-context)<a href="https://agentmods.dev/skills/taizen-ai/taizen-claude-plugins/session-context"><img src="https://agentmods.dev/badge/skills/taizen-ai/taizen-claude-plugins/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.00025 | $0.00901 |
| Opus 5 | $0.00013 | $0.00451 |
| Sonnet 5 | $0.00005 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Context Skill
Automatically gather context about the current user to personalize all subsequent outputs.
Purpose
Identify the current user and gather context about their role, team, and responsibilities to personalize all subsequent interactions and outputs.
Note: This is a background skill that runs automatically when other skills need user context. It does not produce visible output and is not meant to be invoked directly by users.
Skills That Reference This Context
The following skills automatically use session-context to personalize their outputs:
account-research- Adapts account briefs to user's rolediscovery-prep- Tailors prep materials to sales methodologysales-coaching- Personalizes coaching to rep's experience levelexecutive-briefings- Adjusts detail level based on senioritybuyer-profiles- Emphasizes relevant personas for user's dealscompetitive-intelligence- Focuses on relevant competitive scenariosemail-sequences- Adjusts tone for user's communication styleoutreach-templates- Personalizes based on user's territory/focus
Related Background Skills
product-context- Provides product positioning and messaging that this skill uses alongside user contextfeedback-collector- Captures corrections to improve personalization accuracy
Required Integrations
Setup: Connect these data sources to enable user context identification.
Data Sources
# SESSION CONTEXT DATA SOURCES
# Configure the sources for user identification
# Enterprise Search (searches across all internal sources)
- source: enterprise_search
connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
data:
- people_directory
- org_charts
- team_membership
# HR / Directory
- source: hr_system
connector: "{{WORKDAY | BAMBOOHR | RIPPLING}}"
data:
- employee_profiles
- job_titles
- departments
- managers
# CRM (for sales user context)
- source: crm
connector: "{{SALESFORCE | HUBSPOT}}"
data:
- user_records
- territory_assignments
- quota_data
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 · 135 lines · 25 tokens per session scan A a1f2317dacf7
session-context is a skill published in the GitHub repository taizen-ai/taizen-claude-plugins (8 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 901 once invoked, about $0.0001 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…