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/fortiumpartners/ensemble/ensemble-sessionlognpx skills add FortiumPartners/ensemble --skill ensemble-sessionloggit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-sessionlog)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-sessionlog"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-sessionlog.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.00031 | $0.00758 |
| Opus 5 | $0.00015 | $0.00379 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
ensemble-sessionlog 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:sessionlog
This Codex skill mirrors the Ensemble slash command /ensemble:sessionlog.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Capture and persist the current session context as a structured markdown log file. Analyzes the conversation to extract key decisions, commands executed, problems encountered, and resolutions reached. Saves to ./SessionLogs/session-DDMMYY-HH:MM.md relative to the current project directory. Useful for preserving session knowledge across context boundaries, onboarding, and audit trails.
Workflow
Phase 1: Session Analysis
1. Conversation Scanning Review the full session conversation history
- Identify all user requests and assistant responses
- Extract commands executed and their outcomes
- Note tool calls and their results
- Flag any errors, retries, or approach changes
2. Context Extraction Extract structured information from the session
- List key decisions made and their rationale
- Identify problems encountered and how they were resolved
- Capture file paths modified or created
- Note any external resources referenced
- Record configuration or environment details relevant to the work
3. Check for Previous Logs Scan for existing session logs to enable incremental logging
- List files in ./SessionLogs/ directory if it exists
- Identify the most recent session log by filename timestamp
- If a previous log exists, scan its content to understand what was already captured
- Focus this session log on new work, decisions, and changes since the last log
4. Determine Output Path Resolve the session log file path
- Determine the current project root directory
- Construct the SessionLogs directory path relative to project root
- Generate the filename using current date and time in DDMMYY-HH:MM format
- Verify the target file does not already exist
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 · 94 lines · 31 tokens per session scan A 191e665d819d
ensemble-sessionlog is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 758 once invoked, about $0.0002 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-30.
Other skills, from other repositories
codebase-memory
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions…
context-recovery
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity…
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
vc-context-discovery
Discover and load all relevant context for the current task. Lists feature group nested files with full paths, loads process/context/ files by domain routing. Called at the start of every agent session.
vc-generate-context
Generate or update the project's authoritative repository context at process/context/all-context.md. Use when repo context is missing, stale, or contradicted by code.