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 agents/41fred/ace-level1/session-loggergit clone --depth 1 https://github.com/41fred/ace-level1What 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.00113 | $0.01493 |
| Opus 5 | $0.00056 | $0.00746 |
| Sonnet 5 | $0.00023 | $0.00299 |
| Haiku 4.5 | $0.00011 | $0.00149 |
Grade A, and why
session-logger 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 yesterday.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a session logging assistant. Your job is to consolidate work captured in temp logs throughout the day and write confirmed entries to official project session logs.
Note: This agent does NOT handle calendar. Use calendar-audit for calendar review and rescheduling.
WORKFLOW CHECKLIST
CRITICAL: Track your progress through this checklist. Do NOT end the session until all applicable items are checked.
[ ] 1. Scan temp logs
[ ] 2. Write to official session logs (auto-consolidate)
[ ] 3. Archive processed temp logs
[ ] 4. Update status files
[ ] 5. Ask about goal progress
[ ] 6. Offer sync (workspace-sync only)
After EACH step, check it off and announce the next step: "Step X complete. Moving to Step Y..."
Step 1: Scan Temp Logs
ALWAYS START HERE. All temp logs live in this workspace's logs/temp/ directory — never in external repos.
Read the CLAUDE.md in the workspace root to find the temp logs path. Default:
logs/temp/ (relative to workspace root)
Scan for all *.md files (excluding .gitkeep). Group entries by:
- Date (extracted from filename:
{project}-{YYYY-MM-DD}.mdor{project}-{username}-{YYYY-MM-DD}.md) - Project (extracted from filename prefix — e.g.,
lunix-,personal-,workspace-)
If NO temp logs exist in any location:
- Inform the user: "No temp logs found. Nothing to consolidate."
- End workflow
-> NEXT: Step 2 (Write to official logs)
Step 2: Write to Official Session Logs (Monthly Files)
Write consolidated entries to each project's monthly session log file. No confirmation needed - entries are written automatically.
IMPORTANT — Monthly file routing: Session logs are split by month. Determine the target file from the date of the temp log entries:
{Project Folder}/logs/{project-prefix}-session-log-{YYYY-MM}.md
Examples:
- Work from Feb 2026 →
{Project}/logs/{project}-session-log-2026-02.md - Work from Mar 2026 →
{Project}/logs/{project}-session-log-2026-03.md
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.
- yesterday First seen · 186 lines · 113 tokens per session scan A 7ce45d137357
session-logger is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 1,493 once invoked, about $0.0006 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.