timeline-report

timeline-report is a skill for Claude Code, Codex from thedotmack/claude-mem. It costs 47 tokens per session (2,812 once invoked), scanned A, original, Apache-2.0.

A project-history report built from claude-mem, a tool that stores notes about earlier coding sessions. It turns those notes into a narrative about how the project developed over time.

In plain words
What is it for?
Use it to write a development timeline, explain a project’s journey, analyze its history, or summarize the work completed so far.
Why use it?
It helps you understand past decisions, changes, and milestones without manually reconstructing the project’s history. It requires the claude-mem worker to be running and to have saved observations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents.

Part of the claude-mem plugin — 17 skills, 1 MCP server shipped together

Good fit Use it to write a development timeline, explain a project’s journey, analyze its history, or summarize the work completed so far.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thedotmack/claude-mem/timeline-report
About the project

Claude-Mem, now presented as Grok Mem, records an agent's work, compresses it with AI, and brings relevant notes into later sessions so the agent can remember decisions and next steps. It is intended for persistent context across agent conversations and supports multiple coding-agent environments. The catalogue add-ons provide the workflows and integrations used to operate this memory system.

thedotmack/claude-mem · 93,603 stars · on GitHub · claude-mem.ai

Install

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.

Any agent
npx skills add thedotmack/claude-mem --skill timeline-report
Clone the repo
git clone --depth 1 https://github.com/thedotmack/claude-mem

Made for: Claude Code, Codex.

Or install claude-mem, the plugin that ships this one along with the rest of its 17 skills, 1 MCP server.

Wrote 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.

agentmods badge for timeline-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/thedotmack/claude-mem/timeline-report/github.svg)](https://agentmods.dev/skills/thedotmack/claude-mem/timeline-report)
Your own site
<a href="https://agentmods.dev/skills/thedotmack/claude-mem/timeline-report"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/timeline-report/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.

agentmods 80×15 button for timeline-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/thedotmack/claude-mem/timeline-report"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/timeline-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,812 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 26 Apr 2026
  • Snyk fail 26 Apr 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 96
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Memory Poisoning · line 200
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.02812
Opus 5 $0.00023 $0.01406
Sonnet 5 $0.00009 $0.00562
Haiku 4.5 $0.00005 $0.00281

Measured 10d ago against content hash 35b625feab3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

timeline-report scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Resolve the worker port** (do this once at the start and reuse `$WORKER_PORT` in every curl call below):
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugin/skills/timeline-report/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Timeline Report

Generate a comprehensive narrative analysis of a project's entire development history using claude-mem's persistent memory timeline.

When to Use

Use when users ask for:

  • "Write a timeline report"
  • "Journey into [project]"
  • "Analyze my project history"
  • "Full project report"
  • "Summarize the entire development history"
  • "What's the story of this project?"

Prerequisites

The claude-mem worker must be running. The project must have claude-mem observations recorded.

Resolve the worker port (do this once at the start and reuse $WORKER_PORT in every curl call below):

WORKER_PORT="${CLAUDE_MEM_WORKER_PORT:-$(node -e "const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.write(String(s.CLAUDE_MEM_WORKER_PORT||fallback));}catch{process.stdout.write(fallback);}" 2>/dev/null)}"

This honors CLAUDE_MEM_WORKER_PORT env, then ~/.claude-mem/settings.json, then falls back to the per-UID default 37700 + (uid % 100) — matching how the worker itself picks its port. Required for multi-account setups (#2101) and any user who has overridden the default port (#2103).

Workflow

Step 1: Determine the Project Name

Ask the user which project to analyze if not obvious from context. The project name is typically the directory name of the project (e.g., "tokyo", "my-app"). If the user says "this project", use the current working directory's basename.

Worktree Detection: Before using the directory basename, check if the current directory is a git worktree. In a worktree, the data source is the parent project, not the worktree directory itself. Run:

git_dir=$(git rev-parse --git-dir 2>/dev/null)
git_common_dir=$(git rev-parse --git-common-dir 2>/dev/null)
if [ "$git_dir" != "$git_common_dir" ]; then
  # We're in a worktree — resolve the parent project name
  parent_project=$(basename "$(dirname "$git_common_dir")")
  echo "Worktree detected. Parent project: $parent_project"
else
  parent_project=$(basename "$PWD")
fi
echo "$parent_project"

Read the full file on GitHub · 212 lines

Changes

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.

  1. 10d ago First seen · 212 lines · 47 tokens per session scan A 35b625feab3e

Subscribe to this mod's changes

timeline-report is a skill published in the GitHub repository thedotmack/claude-mem (93,603 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 2,812 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

hivemind-goals

Create, track and update team goals + KPIs via the Deeplake virtual filesystem at memory/goal/ and memory/kpi/. Use whenever the user mentions a goal, objective, KPI, target, milestone, or asks to track progress on something measurable. ALSO use when the user says "task", "todo", "work item", "remind me to", "fix X"…

activeloopai/hivemind · 113 tokens

hivemind-memory

Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.

activeloopai/hivemind · 33 tokens

hivemind-memory

Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.

activeloopai/hivemind · 33 tokens

hivemind-graph

Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of…

activeloopai/hivemind · 105 tokens

hivemind

Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.

activeloopai/hivemind · 32 tokens

dejavu-rules

A conversation-based manager for rules stored in CLAUDE.md, a project file that tells the coding assistant how to work. It can add, edit, remove, and review those rules.

cmg8431/claude-dejavu · 56 tokens