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 flonat/flonat-research --skill session-loggit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/session-log)<a href="https://agentmods.dev/skills/flonat/flonat-research/session-log"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/session-log.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00848 |
| Opus 5 | $0.00026 | $0.00424 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
session-log 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Log Skill
Automatically create timestamped progress logs for research sessions.
Purpose
Based on Scott Cunningham's session workflow: “Progress logs are my autosave of the workflow.” When sessions end or crash, the next AI client can read logs and pick up exactly where you left off.
When to Use
At the end of any significant work session, or when asked to "log this session" or "update progress".
Workflow
Step 1: Identify Projects Touched
Before writing anything, inventory which projects were affected during this session. A "project" is any directory with its own CLAUDE.md or log/ directory. Common splits:
| Scope | Where the log goes |
|---|---|
| Work inside a specific project | That project's log/ |
| Global infrastructure (skills, hooks, rules, settings) | Task Management's log/ |
| Course/module-level changes (reorganisation, new CLAUDE.md) | That module's log/ |
Signs of a multi-project session:
- Files changed in AI client infrastructure (skills, hooks, settings) → global/infrastructure log
- Files changed in the CWD project → project-specific log
- Files changed in a parent or sibling directory → check if that's a separate project
Step 2: Create One Log Per Project
For each project identified in Step 1:
- Read existing context — check that project's
.context/current-focus.mdand recentlog/entries - Create
log/directory if it doesn't exist - Write the log to
log/YYYY-MM-DD-HHMM.mdwithin that project - Scope the content — each log only covers what happened in that project, not the whole session
If there's only one project, this reduces to a single log (the common case).
Step 3: Cross-Reference
When multiple logs are created, add a brief cross-reference at the top of each:
> Also logged: [other project name] — `[relative or absolute path to other log]`
This lets a future session in one project discover that related work happened elsewhere.
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.
- 4d ago First seen · 100 lines · 52 tokens per session scan A 13c867e9aba7
session-log is a skill published in the GitHub repository flonat/flonat-research (132 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 848 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
buffer-sizing
Calculate project, feeding, and resource buffers — shared with implementation-planning.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
speckit-companion-specify
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-specify/SKILL.md.