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 skills/ancoleman/ai-design-components/displaying-timelinesnpx skills add ancoleman/ai-design-components --skill displaying-timelinesgit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote 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/ancoleman/ai-design-components/displaying-timelines)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/displaying-timelines"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/displaying-timelines.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.00075 | $0.02338 |
| Opus 5 | $0.00037 | $0.01169 |
| Sonnet 5 | $0.00015 | $0.00468 |
| Haiku 4.5 | $0.00007 | $0.00234 |
Grade A, and why
displaying-timelines 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.
How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Displaying Timelines & Activity Components
Purpose
This skill enables systematic creation of timeline and activity components, from simple vertical timelines to complex interactive Gantt charts. It provides clear decision frameworks based on use case and data characteristics, ensuring optimal performance, real-time updates, and accessible implementations.
When to Use
Activate this skill when:
- Creating activity feeds (social, notifications, audit logs)
- Displaying timelines (vertical, horizontal, interactive)
- Building Gantt charts or project schedules
- Implementing calendar interfaces (month, week, day views)
- Showing chronological events or historical data
- Handling real-time activity updates
- Requiring timestamp formatting (relative, absolute)
- Ensuring timeline accessibility or responsive behavior
Quick Decision Framework
Select component type based on use case:
Social Activity → Activity Feed (infinite scroll, reactions)
System Events → Audit Log (searchable, exportable, precise timestamps)
User Notifications → Notification Feed (read/unread, grouped by date)
Historical Events → Vertical Timeline (milestones, alternating sides)
Project Planning → Gantt Chart (dependencies, drag-to-reschedule)
Scheduling → Calendar Interface (month/week/day views)
Interactive Roadmap → Horizontal Timeline (zoom, pan, filter)
For detailed selection criteria, reference references/component-selection.md.
Core Implementation Patterns
Activity Feeds
Social Feed Pattern:
- User avatar + name + action description
- Relative timestamps ("2 hours ago")
- Reactions and comments
- Infinite scroll with pagination
- Real-time updates via WebSocket
- Reference
references/activity-feeds.md
Notification Feed Pattern:
- Grouped by date sections
- Read/unread states with indicators
- Mark all as read functionality
- Filter by notification type
- Action buttons (view, dismiss)
- Reference
references/notification-feeds.md
What ships with it
32 files 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.
- assets/README.md 526 B
- examples/audit-log-viewer.tsx 215 B
- examples/calendar-scheduler.tsx 211 B
- examples/milestone-timeline.tsx 214 B
- examples/notification-center.tsx 214 B
- examples/project-gantt.tsx 222 B
- examples/react-chrono-timeline.tsx 267 B
- examples/realtime-activity.tsx 221 B
- examples/responsive-timeline.tsx 230 B
- examples/social-activity-feed.tsx 273 B
- outputs.yaml 26 KB
- references/accessibility-patterns.md 350 B
- references/activity-feeds.md 325 B
- references/audit-logs.md 309 B
- references/calendar-patterns.md 248 B
- references/component-selection.md 422 B
- references/gantt-patterns.md 316 B
- references/horizontal-timelines.md 308 B
- references/interactive-timelines.md 292 B
- references/library-comparison.md 912 B
- references/notification-feeds.md 338 B
- references/performance-optimization.md 297 B
- references/real-time-updates.md 311 B
- references/responsive-strategies.md 302 B
- references/timestamp-formatting.md 285 B
- references/vertical-timelines.md 330 B
- scripts/benchmark_timeline.js 342 B runs code
- scripts/format_timestamps.js 330 B runs code
- scripts/generate_gantt_data.py 404 B runs code
- scripts/generate_timeline_data.py 337 B runs code
- scripts/simulate_realtime.js 317 B runs code
- scripts/validate_timeline_accessibility.js 325 B runs code
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 · 402 lines · 75 tokens per session scan A 5abb06c38da9
displaying-timelines is a skill published in the GitHub repository ancoleman/ai-design-components (518 stars, last pushed 8mo ago), licensed MIT. It adds 75 tokens to every session and 2,338 once invoked, about $0.0004 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-30.
Other skills, from other repositories
ui-ux-laws
Priority-ordered rulebook of core UX/UI laws, cognitive-psychology principles, Nielsen's usability heuristics, and accessibility requirements that Claude must actively apply (not just cite) whenever it designs, builds, redesigns, reviews, or critiques any user interface — websites, web/mobile apps, dashboards, forms…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
johnny-suede-design
Suede Labs AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to…