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 commands/xiaolai/echo-sleuth-for-claude/timelinegit clone --depth 1 https://github.com/xiaolai/echo-sleuth-for-claudeWrote 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/commands/xiaolai/echo-sleuth-for-claude/timeline)<a href="https://agentmods.dev/commands/xiaolai/echo-sleuth-for-claude/timeline"><img src="https://agentmods.dev/badge/commands/xiaolai/echo-sleuth-for-claude/timeline.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.1 | $0.00000 | $0.00392 |
| Opus 5 | $0.00000 | $0.00196 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
timeline 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 6d 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
Show a chronological timeline of work on the current project, combining Claude Code session history with git history.
Optional arguments: $ARGUMENTS
Launch the recall agent via the Task tool with the following context:
- Focus: timeline / project history
- Task: Build a chronological timeline of all work on the current project
- Combine: Claude Code sessions (what was discussed, tried, failed) + git commits (what shipped)
- Default limit: 50 sessions, 30 days of git history
- Parse any flags: --limit N, --since YYYY-MM-DD from: $ARGUMENTS
The agent should:
- List all sessions for the current project
- Check if this is a git repo (
git rev-parse --is-inside-work-tree). If yes, get git history. If not, skip git data and build the timeline from session data only. - Merge both timelines chronologically, correlating by timestamp (session-only if not a git repo)
- Enrich key sessions (high message count, error-heavy, or milestones) with stats
- Present as a timeline with clear markers for milestones
- If not a git repo, note at the top: "No git repository detected — timeline is based on session data only."
Output format:
# Project Timeline: [project name]
Branch: [current branch]
Period: [earliest] → [latest]
Total: [N sessions, M git commits]
### [YYYY-MM-DD] — [Session summary]
Branch: [branch] | Messages: [N] | Files: [N]
[1-2 sentence description]
Git: [commit hash] [commit message]
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.
- 6d ago First seen · 39 lines · 0 tokens per session scan A dbbabc4b7165
timeline is a command published in the GitHub repository xiaolai/echo-sleuth-for-claude (9 stars, last pushed 12d ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 392 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.