Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Felpix-Studios/social-science-research/plugin install social-science-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/felpix-studios/social-science-research/session-log)<a href="https://agentmods.dev/skills/felpix-studios/social-science-research/session-log"><img src="https://agentmods.dev/badge/skills/felpix-studios/social-science-research/session-log/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/felpix-studios/social-science-research/session-log"><img src="https://agentmods.dev/badge/skills/felpix-studios/social-science-research/session-log.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.00525 |
| Opus 5 | $0.00014 | $0.00262 |
| Sonnet 5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 9d 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.
What it actually says
Session Log
Create or update a session log to capture decisions, changes, and progress.
Input: $ARGUMENTS — create for a new log, update to append to the most recent log, or a description of what to log.
Step 1: Determine Mode
- If
$ARGUMENTSiscreateor no session log exists inquality_reports/session_logs/→ Create mode - Otherwise → Update mode
Step 2: Create Mode
- Read the most recent plan from
quality_reports/plans/(if any) to auto-populate Objective - Run
git log --oneline -10to see recent commits - Read the format template via Bash:
cat "${CLAUDE_PLUGIN_ROOT}/skills/session-log/assets/session-log.md"(templates ship inside the plugin and are not copied into the project) - Save to
quality_reports/session_logs/YYYY-MM-DD_short-description.md - Populate:
- Objective: from plan or
$ARGUMENTS - Status: IN PROGRESS
- Design Decisions: from plan or argument (prefix each with
Decision:) - Changes Made: from recent git log if relevant
- Objective: from plan or
Tell the user the log was created and where.
Step 3: Update Mode
- Read the most recent session log in
quality_reports/session_logs/ - Run
git diff --statandgit log --oneline -5to see what changed since last update - Append new entries to the appropriate sections:
- Changes Made: new files modified (from git diff)
- Design Decisions: if
$ARGUMENTScontains decision text, add asDecision: [text] - Incremental Work Log: add timestamped entry for current work
- If all planned work is complete, update Status to COMPLETED
Tell the user what was added to the log.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 48 lines · 27 tokens per session scan A 1853780364ce
session-log is a skill published in the GitHub repository Felpix-Studios/social-science-research (8 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 525 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…