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 mostafa-drz/claude-skills --skill day-timelinegit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/day-timeline)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/day-timeline"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/day-timeline/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/mostafa-drz/claude-skills/day-timeline"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/day-timeline.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.00120 | $0.01998 |
| Opus 5.5 | $0.00048 | $0.00799 |
| Sonnet 5.5 | $0.00024 | $0.00400 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
day-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 1mo 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Day Timeline
Reconstruct one workday, hour by hour, from every connected source — grounded in truth, every entry traceable to its evidence. Output is a Markdown file plus a self-contained HTML page.
This timeline is holistic and source-agnostic. It is not a coding log. A day is made of meetings, decisions, messages, emails, reviews, writing, research and errands as much as it is of code. Weight every kind of work equally; let the evidence — not an assumption about what the user does — decide what fills the day.
Core principles (do not skip)
- Evidence-based, reference-based. Every timeline entry must trace to a real artifact — a calendar event, an email, a chat message, a tracker ticket, a doc, a commit or PR, a Claude Code session. Quote verbatim; never paraphrase into invention.
- One timezone. Sources disagree: many APIs (email, chat, Claude Code sessions) return UTC; calendars usually return local time. Determine the user's local zone, convert everything to it before sorting. This is the #1 source of ordering bugs — get it right.
- Snapshots ≠ current state. Where a session, doc, or thread ended is not where the work is. Before recommending anything, verify live status (see Phase 5).
- Pull holistically, then reconcile. No single source is the truth — each has gaps another fills. Gather all connected sources, cross-reference, reconcile. Do not privilege one tool as the spine of the day.
- Recommendations are not only dev work. A recommended action can be a decision, a message, a reply, a review, a nudge, meeting prep, an errand — whatever the day actually left open.
Input
Resolve the argument to one date:
today(default) ·yesterday· or an explicitYYYY-MM-DD.- Today vs. past day decides the output shape:
- Today → timeline + recommendations + follow-ups.
- Past day → timeline only (recommendations and follow-ups are forward-looking and only meaningful for the current day).
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.
- 1mo ago First seen · 163 lines · 120 tokens per session scan A 48c41fa9dc9e
day-timeline is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 20d ago), licensed MIT. It adds 120 tokens to every session and 1,998 once invoked, about $0.0005 per session on Opus 5.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-12.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.